External collaboration is where a collaboration platform either shines or leaks. The features are mature; the failure is organisational — nobody owns the front door. This chapter hands the door to someone, gives them a ritual, and sets an alarm for when the door forgets its job.
Two door designs
External access comes in two shapes, and choosing matters more than configuring.
- Guest accounts — a person from another company joins one named room as themselves. Precise conversation-by-conversation control, with identifiable membership and a name you can audit.
- Federated / open channels — your domain trusts theirs, and meetings and chats connect without invites to each individual. Friendly to frequent partners; coarser everywhere else, including audits.
Field note
Govern each guest with the same three ingredients, repeated from memory: purpose (their project), lifespan (end date), scope (how many rooms). A guest record missing one of the three is a future outage report waiting to be filed by someone in legal.
Provisioning and review
The ritual has two steps. First, no external person is provisioned until their record is complete — purpose, lifespan, scope. Second, an internal sponsor — someone inside your office — owns their departure as well as their arrival. Then the door needs a period of self-checking, which is where reports earn their keep.
- Quarterly: list every guest, match each to a sponsor, remove the ones whose project has closed.
- Alerts: a new guest in a workspace, a guest removed from a protected room, or a share link changed to broad.
External collaboration earns trust only with bookkeeping. Set the ritual up properly, front-load the activation, and the auditing trail is a five-second glance instead of a two-week mystery.
