Overview
A member of an organization is a user. Users have unique email addresses and can be members of multiple organizations.
Owners and admins of an organization can grant users access to one or more accounts (or no accounts at all) and assign one of three roles.
User creation
A user is created when a person registers their profile with Intuiface. Typically, this registration process occurs in response to an invitation sent in one of two circumstances:
- Owners or admins of an organization grant someone access to an account.
This makes the user a member of that account's organization. - Owners of a Headless CMS base grant someone access to that base.
Headless CMS bases are associated with users, not accounts. In this case, the user is not made a member of any organization.
Inviting a user to access one or more accounts
In the Users Dashboard, the organization owner or one of its admins should perform the following steps.
- Click the "Invite a user" button in the upper-right corner of the screen.
- Complete the form, entering the following information:
- Email address of the person you are inviting.
- The role you are assigning
(Only Platform Enterprise organizations can assign the Admin role) - The one or more accounts to which the person is being invited
(Only Platform Enterprise can assign a user to more than one account.)
- Click the "Send invitation email" button at the bottom of the screen.
If the user already exists, they will receive an email inviting them to join the organization and access the specified accounts. If the user does not exist, they will receive an email directing them to register their profile with Intuiface.
Inviting a user to access a Headless CMS base
See the Headless CMS user invitation process for details.
If the user already has an Intuiface profile, they will receive an email inviting them to access the base. If the user does not have a profile, they will receive an email directing them to register with Intuiface. In either case, this process does not associate the user with an organization.
User Roles
A user's role determines which capabilities they have and the scope of those capabilities. The role is specified during the invitation process initiated by an Owner or Admin of an organization, and can be changed by the Owner and Admins at any time.
"User" role
The "User" role is the baseline role for a member of an organization. With one exception—see the Owner role below—every organization member starts with the User role. Users are granted account access by the owner and/or admins of the organization containing that account.
Here are the capabilities of users with the User role. All capabilities are limited to the accounts to which the user has been assigned.
- Edit experiences
- Deploy experiences and manage Players
- Activate/release Composer and Player licenses
- Manage data points, create charts, and publish dashboards for Analytics
- Create credential keys (for their account)
A user can also create/edit Headless CMS bases. For this capability, the user does not need to be part of any organization or account. The relationships between users and Headless CMS bases are organization and account-independent.
"Admin" role
NOTE: This role is limited to Platform Enterprise organizations.
The "Admin" role is a superset of the "User" role. Its scope is one organization: a profile with the Admin role in one organization can have the User role in another organization. This role can only be granted by the organization's owner.
An organization can have any number of admins.
Here are the additional capabilities of users with the Admin role:
- Access content and data across all of the organization's accounts
- Loan licenses in the organization's primary account to other accounts in the same organization and retrieve those licenses as needed.
- Share experiences with accounts in any organization
- Access the Audit Trail for the organization
- Create / edit / delete accounts for the organization
- Invite / edit / remove users from any account in the organization
- Assign the "Admin" role to users
"Owner" role
The "Owner" role is a superset of the "Admin" role. Its scope is the organization created when a Trial was started or a Platform subscription is purchased.
An organization is limited to one owner.
Here are the additional capabilities of users with the Owner role:
- Purchase / stop license subscriptions
- Manage payment cards
- Access invoices
Comments
0 comments
Please sign in to leave a comment.