Groups and roles
Groups and roles decide what each person in your organization uses and administers. Each person has a role; whoever has the Custom role gets what the custom roles of their groups allow. Changes reach the chats in a couple of minutes.
Each person’s role
Section titled “Each person’s role”Each person has exactly one:
| Role | What they can do |
|---|---|
| Primary Owner | Owns the account and can do everything an Owner does. There is only one, and only they can transfer the account. |
| Owner | Manages the whole organization: members, groups and roles, billing, connectors, skills and the rest of Organization. |
| Admin | Manages members and seats and sees Analytics without the spending. Doesn’t see billing, groups, roles, skills or connectors. |
| User | Uses what the organization enables for them and every enabled model. No administration. |
| Custom | Gets what the custom roles of their groups give them: models, capabilities and areas to administer. |
The role is changed in Organization → Members (see Managing members). Nobody changes their own role. Organization settings shows in the account menu only for Owners.
Groups
Section titled “Groups”Groups are collections of members that can share roles. The table has Name, Members (how many), Roles (the labels), Source and Visibility. Above it, Search by name filters the list, the Source filter shows only the Manual or only the Directory groups, and Sort orders it by Name A-Z (the default) or Most members. The list shows 25 groups per page.
To build one:
- Click Add group and type the Group name. Adding a group only asks for the name.
- With Edit, in the row’s ⋮ menu, you add people under Members (the dropdown says Add member…) and change the name.
Under Source each group says where its members come from: Manual ones you manage yourself in Nouter, and Directory ones are groups whose members come from your directory and are managed there, so their name and members aren’t edited in Nouter.
Visibility settings
Section titled “Visibility settings”When you create or edit a group, Visibility settings decide who can do three things with it. Each one is for the Group members, for Everyone in the organization, or for no one:
- Discover this group: find it by name. It doesn’t show its members or its roles.
- Share resources with this group: share blueprints with it.
- See group members: see who’s in it, with their name and email.
All three start off, so a group made only to give a role isn’t a place to share with until you decide it. The Visibility column sums it up (for example, “Discover: Everyone”). Owners and custom roles with Identity & Access always see every group. Turning off Share resources with this group stops new sharing; what was already shared stays.
Delete takes a group off every role. The confirmation says so: “Deleting the group takes it off every role. Its members keep their accounts.”
Custom roles
Section titled “Custom roles”A custom role decides what the people in its groups can use and administer. The table has Name, Groups (the labels of the groups that have it), Admin access (the areas it administers, and the ones it only views) and Created. Above the table, Search by name filters the list and Sort orders it by Name A-Z (the default) or Newest; it shows 25 roles per page. To build one, click Add role, type the Role name and a Description, and with Edit pick the Groups (the dropdown says Add group…) that receive it. The editor has two tabs:
- Capabilities: choose All capabilities, All generally available or Only selected, and then mark Web fetch, Web search, Share workspaces with people, Share workspaces that use connectors and Share blueprints. The first two forms pick up new capabilities as they come out.
- Permissions: for each area (Identity & Access, Billing, Analytics, Privacy, User Management and Libraries) choose No access, Can view or Can manage; some areas offer only one of the last two. With Can view, the page opens without the buttons that write and says “You have view-only access.” Can manage on Identity & Access lets the role edit groups and roles, including its own: give it only to administrators you trust.
A role is always assigned to groups, never to a person. A person in several groups gets the union of their roles, and one role can’t take away what another grants. Roles apply only to people with the Custom role. Delete takes a role off the models it was available to (the confirmation says so: “Deleting the role takes it off the models it was available to. Its groups stay.”).
When there are roles but nobody is Custom, a yellow notice appears above Roles: “Map groups to roles and then set members’ role type to Custom.”, with Go to Members.
Which models a role can use is set in Organization → Models, in the Available to column (see below). If someone with Can view opens a role or a group, View shows the same form, read-only.
Which models each person uses
Section titled “Which models each person uses”Each role’s models are chosen in Organization → Models, in the Available to column (see Which models your organization uses):
- Whoever isn’t Custom sees every enabled model.
- A Custom member sees the enabled models that are set to All roles plus the ones that share one of their roles.
- A Custom member with no roles sees only the models set to All roles.
If a chat asks for a model that isn’t allowed for that person, it runs on the default model if that one is allowed, and otherwise on the first allowed one. If none is left, the chat says so: “Your organization hasn’t given you access to any model.”