Skip to main content
Access profiles ensure only users in designated groups can request access to particular roles. This prevents unauthorized access requests and maintains security boundaries across your applications.

Understanding Access Profiles

Access profiles answer the question: “Who is allowed to request this role?” They work by mapping Serval groups to roles. When a user requests access, Serval checks whether they belong to a group that’s allowed to request that role. A role can be linked to more than one access profile. A user who matches any linked profile can request the role, so linking additional profiles widens who is allowed to request it.
Example: You can create an “Engineering” profile that only allows members of your engineering teams to request access to production databases.
Configure the following settings to define which users can request specific roles:

Name

The user group identifier from Serval. Must match existing Serval group naming conventions.

Description

Optional context about the profile’s purpose, target user population, or usage guidelines.

Associated Groups

Additional Serval groups included in this access profile. Use this to combine multiple groups under a single access policy.

Associated Roles

IdP groups linked to this profile. These determine which roles become requestable for users matching this profile.

User fields

Match users by a user profile field. Built-in fields (Department, Job title, Email, Timezone, and Locale) are available alongside your custom text, select, and Yes/No fields. Pick a field, then choose the values that qualify (for example, everyone whose Department is Engineering, or everyone whose Is manager is Yes).

Configure a Profile in Settings

New access profile dialog with name, description, and matching criteria for specific groups, workspace members, and user fields

Create an access profile in Settings → Access Profiles


Create an Access Profile

1

Name the profile

Name: The user group identifier from Serval. Must match existing Serval group naming conventions.Description: Optional context about the profile’s purpose, target user population, or usage guidelines.
2

Add associated groups

Associated Groups: Additional Serval groups included in this access profile. Use this to combine multiple groups under a single access policy.
For example, combine “Engineering-Frontend” and “Engineering-Backend” groups into a single “Engineering” profile.
3

Link IdP groups

Associated Roles: IdP groups linked to this profile. These determine which roles become requestable for users matching this profile.
4

Save the profile

Click “Save profile” to make it available for role configuration

Manage Access Profiles

Once created, access profiles can be managed centrally and applied to multiple roles across your organization. To access profile management, open the workspace in the sidebar, then go to Settings → Access Profiles. In a resource review preview, Workspace members shows Any role on this workspace when the current-workspace criterion has no role filters. If you restrict the criterion to specific roles, the preview lists those roles instead.

What You Can Do

Choose a default profile, then choose what it applies to: Roles, Workflows, Forms, and Skills. Resources of each selected kind that you create from now on join the profile automatically; a copy of a form or workflow keeps its source’s audience instead. New roles become requestable by the people the profile includes, and new workflows, forms, and skills are limited to those people instead of everyone in the organization. A workspace that hasn’t changed this applies its default to new roles only. To change the selection later, select Change what it applies to under Default access profile. If you make another profile the default, resources that joined the old default automatically move to the new one for the kinds you select. A resource the new default excludes keeps the old profile.The default for roles is typically your broadest user group (e.g., “All Employees”).
Modify profile settings. Changes apply to all roles using that profile, making it easy to update access permissions organization-wide.
See which roles currently use each profile. This helps you understand the impact before making changes.
Add or remove roles that the profile should apply to. Reuse profiles across similar access patterns for consistency.

Profile Examples

All Employees

Groups: company-all-employees
Purpose: Standard company-wide applications like Slack, Google Workspace
Use for: Access that every employee should be able to request

Engineering

Groups: eng-frontend, eng-backend, eng-infrastructure
Purpose: Engineering tools and production access
Use for: Developer tools, code repositories, staging environments

Finance Team

Groups: finance-accounting, finance-payroll
Purpose: Financial systems and sensitive data
Use for: Accounting software, payment processors, financial dashboards

Contractors

Groups: contractor-engineering, contractor-design
Purpose: Limited access for external workers
Use for: Non-sensitive tools and resources appropriate for contractors

Best Practices

Map to org structure

Create profiles that mirror your actual organizational structure. This makes it intuitive for admins to assign the right profiles.

Use broad profiles for common access

Create an “All Employees” profile for widely-used applications. This reduces administrative overhead.

Combine groups thoughtfully

Group teams with similar access needs together. For example, all engineering groups can share an “Engineering” profile.

Document profile purposes

Write clear descriptions so admins understand when to use each profile when configuring new roles.

Restricting workflows and skills

Access profiles can also control who can request a workflow and who a help desk skill applies to. With no profiles linked, a skill reaches every requester. A new skill starts linked to the workspace’s default profile when the default applies to skills (see Set a default profile). To narrow it, link one or more access profiles to the skill from its editor: the skill then reaches only requesters who match a linked profile, using the same membership rules a profile uses to decide which roles it makes requestable. Linking more profiles widens the audience to anyone who matches any of them.

Restricting knowledge bases

Access profiles can also control who the help desk agent can surface a knowledge base to. Add a knowledge base to a profile, and the agent uses that base’s content only for requesters who match the profile.
1

Open the profile

Open the workspace in the sidebar, then go to Settings → Access Profiles and open the profile.
2

Add the knowledge base

Under Knowledge Bases, click Add knowledge base and select the base. The change applies when you add it.
How a grant works:
  • The grant restricts the base. A knowledge base with no profiles is available to anyone in the org. When you add it to a profile, only requesters who match that profile get answers from it.
  • More profiles widen the audience. If you add the same base to several profiles, a requester who matches any of them gets answers from it.
  • Pages and folders can inherit the grant. In Visibility, turn on Inherit parent visibility to include the parent audience and add profiles for that page or folder. Turn it off to use only its own audience. Child settings do not change the base or parent. See Help desk audience.
  • It’s the same setting as the base’s visibility. Adding a base to a profile here gives the same result as adding the profile in the knowledge base, under the base’s actions menu → Visibility. You can see and change the grant from either place.
  • It controls the help desk audience only. Workspace roles still decide who can view and edit the base inside Serval. See Access control.
Removing the last profile from a knowledge base makes the base available to anyone in the org again. To keep a base restricted while you change its audience, add the new profile before you remove the old one.
You can’t add a knowledge base whose permissions are synced from its connected source, such as ServiceNow. The picker shows it as Access managed by source, because the source decides who can see it. If someone turns on permission sync for the source while you add the base, Serval refuses the add and does not save the grant.