Abbey Docs
  • 👋Welcome
  • Getting Started
    • Quickstart
    • Step-by-Step Tutorials
      • AWS: Managing Access to Identity Center Groups
      • AWS: Managing Access to Identity Center Permission Sets
      • AWS: Managing Access to IAM Groups
      • Azure AD: Managing Access to Groups
      • Confluent: Managing Access to Kafka ACLs
      • Databricks: Managing Access to Managed Tables in Unity Catalog
      • Databricks: Managing Access to Groups
      • GitHub: Managing Access to Teams
      • Google Cloud: Managing Access to Groups
      • Google Workspace: Managing Access to Google Groups
      • Kafka: Managing Access to ACLs
      • Okta: Managing Access to Groups
      • Postgres: Managing Access to Roles
      • Snowflake: Managing Access to Tables
      • Tabular: Managing Access to Apache Iceberg Roles
      • Tailscale: Managing Access to ACLs
      • Vault: Managing Access to Groups and Policies
      • Integrating Abbey with Terraform Cloud
      • Using Abbey with Atlantis
      • Using Abbey with Spacelift
    • Starter Kits
  • How Abbey Works
    • How Abbey Works
    • Key Concepts
  • Build a Grant Kit
    • Get a Starter Kit
    • Connect a Repo
    • Create a Grant Kit
    • Link Identities
    • Write Access Policies
    • Deploy Your Grant Kit
    • Request Access
    • Approve or Deny Access Requests
  • Use Cases
    • Time-Based Access
      • Expire After a Duration
      • Expire At a Specific Time
    • Approval Workflows
      • Using a Single Approval Step
      • Using Multiple Approval Steps
      • Conditionally Skip Approval Steps
  • Admin
    • User Roles
    • Sign-in and MFA
      • Sign-in Methods
      • Multifactor Authentication (MFA)
      • Enabling Single Sign-On
    • Sources
      • PagerDuty
      • Directory Sync
    • End User Notifications
    • Manage API Tokens
  • Reference
    • Grant Kits
      • Workflows
      • Policies
      • Outputs
    • Referencing Users and Groups
    • Linking Application Identities into Abbey
      • Why do I need to link application identities?
      • How do I Link Application Identities?
      • Supported Application Identity Types and Schemas
      • Application Data Object
    • Access Policies
      • Types of Access Policies
      • Policy Bundles
      • Inline Policies
      • Helper Functions
      • Policy Examples
    • Terms of Service
    • FAQ
      • Troubleshooting
  • Resources
    • Abbey Labs
    • Terraform Registry
    • GitHub
    • System Status
    • Privacy Policy
    • Logo
Powered by GitBook
On this page
  • Admin
  • Member
  • How to Assign a Role
  • New User
  • Existing User
  1. Admin

User Roles

PreviousConditionally Skip Approval StepsNextSign-in and MFA

Last updated 1 year ago

Abbey lets you distinguish between roles so that you can ensure the integrity of your organization's settings by preventing accidental or unauthorized changes.

There are two types of users in Abbey: Admins and Members.

Admin

Admin roles provide members with full access to manage all aspects of the organization, including its resources, memberships, and settings. This includes the capabilities to add, update, and delete Grant Kit Resources, as well as modify Abbey Settings.

Member

The standard Member role within an organization allows users to view Grant Kit Resources and handle access requests, including both requesting and approving them, allowing participation and collaboration within the organization.

Action
Admin
Member

View Resources

✅

✅

Update/delete Resources

✅

❌

Request Access

✅

✅

Approve Access

✅

✅

Manage Abbey

✅

❌

How to Assign a Role

You must be an admin to assign roles.

New User

  1. Click on the organization name on the side menu bar

  2. Click Manage Organization to open the modal

  3. Click on Members > Invitations > Invite

  4. Type the email address of the user you are trying to invite

  5. Select the desired Role for the user

  6. Click Send Invitations button

Existing User

  1. Click Manage Organization to open the modal

  2. Click on Members > Members

  3. Find the user in the list of users

  4. Use the Role dropdown to configure the desired role for the user

Click on the organization name on the side menu bar