Team access when someone leaves

Almost everywhere, work is handed over as a secret. A password, a laptop, a disk image: once it is out of your hands it is out for good.

So the honest question to ask first is the leaving one. An approach with nothing to revoke is an approach where a departure means changing every password by hand.

Read the rows as approaches rather than as product names. The last row is ours, and you can check every cell in it: each one has code behind it that you can open.

Where an approach has no notion of a second person, the cell says so. An invented answer would be worse than a blank one.

A role applies to the whole workspace and answers one question: how much this person may change.

• Operator

  Makes profiles in the employer's quota, shares them and deletes them. The shared creative library takes additions and deletions from any member.

• Manager

  Plus the shared working stock: groups, proxies, flows, schedules and requests on the Proxy providers screen.

• Admin

  Plus billing, the team, History and other people's machines.

• Owner

  Everything, and the one seat nobody can take away.

Two colleagues opening one profile in the same minute produce two live sessions of one account from two places. So a profile is busy for everyone at once, not only on the machine where it was opened. With the app signed out, or the server out of reach, it opens the profile rather than stopping your work, and two colleagues can then land on one account.

A machine pulled from the wall does not hold a profile forever: three minutes later it is open to the team again, and you have nobody to ask.

Removal and a departure by choice run one path, and everything below happens at once rather than in pieces. There is no half of it: either all of it comes back or none of it does.

• Shares are cut

  Their access to other people's profiles goes, and access to the profiles leaving with them.

• Their profile is yours again

  A profile they were holding opens for you at once, though the list keeps showing it busy for a little while.

• A date splits the profiles

  What was made inside the workspace passes to the owner, and what they brought goes with them.

• Working proxies stay behind

  A leaving profile does not take the employer's library proxy with it, nor the password saved for it.

• Unused invites die

  A second code on the same address stops being a way back in.

• Machines and group access go

  Devices are unlinked, and the group restriction does not travel to the next employer.

A colleague leaving does not empty the history: the rows stay where they are.

Renaming a profile today does not rewrite last week.