Access and people
How people sign in, join folders and get the skills and tools meant for them.
The Access and people module decides who is in your workspace and what each person reaches. People sign in with their company account, belong to groups, and get skills, tools and notebooks through the folders and grants those groups hold.
| Who | What they do in this module |
|---|---|
| Everyone | Sees their groups, asks to join folders, and checks why they have each skill or tool |
| Folder managers | Give groups and people a role on their folder and answer requests to join it |
| Skill owners and authors | Decide who uses a skill, who works on it, and its access levels |
| Admins | Invite people, run groups, connect single sign-on and the directory, and see anyone's access |
Basics
Workspaces and roles
Owner, Admin, Member and Guest
Invite people
Send invitations and follow the ones still open
Groups
Group pages, Everyone, Guests and directory groups
Folders and their managers
Each team's skills, tools and notebooks in one place
Roles and grants
What Use, Author, Review and Manage mean, and how to give them
Features
Ask to join folders
Discoverable folders and requests to join them
Access levels and collections
On by default, required, blocked, and sets of skills
View as a person
Person pages and Explore as someone else sees it
Single sign-on
Sign in through your company's identity provider
Google directory sync
People and groups from Google Workspace
SCIM provisioning
Your identity provider creates and removes people and groups
REST API tokens
Personal tokens for scripts and integrations
What admins can switch off
Admins switch these under Admin, Features, in the Access and people section. Groups, folders, invitations and grants are part of every workspace.
| Feature | Switch |
|---|---|
| Ask to join spaces | On by default |
| Access levels and collections | On by default |
| View as a person | On by default |
| Single sign-on | On by default |
| Google directory sync | On by default |
| SCIM provisioning | On by default |
| REST API tokens | On by default |
A feature that is off disappears from the hub, and Parcel refuses it everywhere else too. What it holds stays stored and comes back when the feature is on again. See Features for how switching works.