Import and export
Rules are per person. Export and import is how a rule moves between people, or between workspaces.
Export
Inbox → Rules → Export writes your rules to a file. Use it to back up a set you have tuned, or to hand a working rule to a colleague.
The export carries conditions, actions and settings. It does not carry execution history — the receiving copy starts with a clean log.
Import
Inbox → Rules → Import reads a file and creates the rules on your account.
Two things to check after importing.
Anything referring to a specific record. A Link action points at a database row. If the export came from another workspace, that row does not exist here and the action needs repointing.
Priorities. Imported rules arrive with the priorities they had. If you already have rules, the two sets can interleave in ways neither was designed for — particularly where one uses Stop processing.
Dry run imported rules too
An imported rule is as untested on your inbox as one you wrote from scratch. It matched somebody else's mail, not yours.
Sharing a rule with the team
There is no shared rule. If everyone needs the same behaviour, one person builds and tests it, exports it, and the others import it. Each copy is then independent — editing yours does not change theirs.