Managing Access
Managing users
Any Admin and Account Owner is able to manage users. However, an admin can grant permissions only for locations where they are an admin themselves, which stops anyone from inviting their way to more access than they have.
Inviting a user
The admin enters the email address, the role, and the locations it applies to.
The console produces an invite link and, separately, an invite key that only the admin sees.
Our identity provider emails the invitation to the address.
The admin sends the invite key to the person through another channel.
The person opens the link, signs in, and enters the invite key.
An invite key works once.
The invite key that is displayed to you in the Management Console is generated in your web browser and only accessible to you. We do not generate or store invite keys on our servers. This is by design, so that we can never gain access to your instances or Management Console account.
Both halves are needed on purpose. The link proves the person controls the email address. The key, sent another way, proves the admin meant to invite this particular person, so a forwarded invitation email is not enough to join your company.
Removing access
Remove a user
Their session ends immediately and they can no longer sign in
Change a user's permissions
Applied while they are signed in, within a few seconds. A user who is offline keeps their previous permissions until they sign in again
Remove an instance
The instance can no longer communicate with the console
To take access away straight away, remove the user rather than lowering their role, then invite them again with the permissions you want. What they built stays: their bridges, data models and the users they invited belong to the company, not to them.
Sessions cannot be ended individually yet, so removing the user is the only way to end a session you do not control.
Last updated