40+ hours saved per hire
Wilbur established a more consistent screening workflow across its hiring process. The time result is not attributed to Team & Access controls alone.
Read the Wilbur storyCollaborative hiring, team & access
Set who administers the account, assign role-scoped teammates to the jobs they own, and let authorised hiring teams review evidence, update stages, and leave internal comments within live access boundaries.
Fictional team workspace
Operations hiring team
Customer perspective from the wider Skill Society workflow
“The Skills Society AI Interview Agent is a fantastic tool—not only for saving time, but also for establishing consistent and fair recruitment standards.”
How collaborative hiring access works
Separate account administration from day-to-day hiring, then combine role assignment and eligible feature access to control what each teammate can see and do.
In the Administrator-only Team & Access workspace, classify people who have already joined the account as Administrators or role-scoped Members. Administrators manage the account and automatically access every active role; Members need explicit assignments.
Account settings and permission management stay with Administrators instead of becoming part of every hiring manager's workspace.
Account responsibility
Step 01Each existing account user has one clear account level, active state, and summary of the hiring work available to them.
Share the hiring work—not the entire account.
Skill Society combines live role assignments and eligible feature permissions so the team can collaborate without weakening account boundaries.
Outcomes from wider Skill Society workflows
Wilbur established a more consistent screening workflow across its hiring process. The time result is not attributed to Team & Access controls alone.
Read the Wilbur storyGTS connected qualification and structured interviews in its wider Skill Society workflow. The time result is not attributed to role permissions alone.
Read the GTS story
William Buck maintained strong candidate satisfaction through its wider graduate screening workflow. The result is not attributed to collaboration controls alone.
Read the William Buck storyStart with one hiring team
These customer outcomes came from broader Skill Society screening and interview workflows. Collaborative Hiring, Team & Access keeps responsibility, visibility, and candidate actions clear around that work.
Questions, answered
These answers reflect the team, role, feature, and candidate-collaboration boundaries currently shipped in Skill Society.
No. Team & Access manages people who have already joined the same Skill Society account. It does not currently include a user invitation flow.
Administrators can access every active role and manage account settings, permissions, role configuration, and other Administrator-only actions. A role-scoped Member can view and operate only assigned active roles, subject to any separate feature permissions and the account subscription.
Yes. An Administrator can assign an active Member to multiple active roles from Team & Access or from each role's Hiring Team panel. The Member's Jobs and Recent Activity views are filtered to those accessible roles.
Yes, for eligible delegated features. Administrators can use reviewer, hiring-manager, or recruiter presets and then adjust each Member's available view or operate capability. The account subscription remains the maximum, and role access and feature access are enforced independently.
No. The current interface assigns roles and eligible feature capabilities, not a literal checklist of pages. Available pages and actions are derived from central Administrator, role, and feature rules so the interface and server enforcement use the same access model.
Yes. Authorised teammates can add internal comments to an accessible candidate application, associate them with the pre-qualification or assessment stage, and include supported attachments. Comments show their author and time and are never sent to the candidate.
Role assignments and removals are read live from the database. A removed Member is blocked on the next request, including direct role URLs and candidate mutations, without waiting for their login token to refresh.
No. An Administrator cannot demote or deactivate themselves from their own controls, and the permission rules prevent an account from losing its final active Administrator. Another Administrator must make an allowed access-level change.