Provisioning Methods
Serval offers multiple provisioning methods to fit the needs of each team and application.
Configure how access is granted:
Linked Groups
Access granted by adding the user to a group in your Identity Provider (Okta, Google, Rippling, Entra) mapped to the role through SCIM.
Example: Add the user to the appropriate Okta group. When access expires, the user is automatically removed.
Custom Workflow
Access granted through a custom process, like using an API to send an email invite or opening a GitHub PR for a Terraform change. [Link to custom workflow process]
Simple: Add or remove users from a GitHub team that controls repository accessMulti-Step: Open a GitHub PR for Terraform group membership, create a Linear task to purchase a license, auto-merge the PR when the task is complete
Direct
Pre-built API provisioning for common applications.
Example: Automatically import Ramp roles and provision access via API.
Manual provisioning
Access granted through a task assigned to the application owner (via ticket or Slack).
Example: Jeff requests editor access to Linear. The assignee adds Jeff as an editor. For 12-hour temporary access, Serval creates a ticket to grant access and another to remove it 12 hours later.
Depending on the way the role is imported, you will have different options for configuring access in order to maximize how effective your tool is: