Manage team access and permissions
Invite team members and assign roles at the organization level. Admin and Member roles control who can manage settings and who can work with redirect rules.
Alice Chen
alice@company.com
Bob Martinez
bob@company.com
Carol Park
carol@company.com
Dave Wilson
dave@company.com
How role-based access control works for redirect teams
Team management uses a role-based model with two roles: Admin and Member, powered by Clerk Organizations. Admins can manage organization settings, billing, and team membership. Members can work with redirect rules and projects within the organization.
Invitations are sent by email and include the assigned role. Pending invitations are tracked on the team dashboard and can be revoked before acceptance. When a user accepts an invitation, they are added to the organization with the specified role and can begin working immediately.
For organizations using single sign-on, Clerk provides SAML 2.0 and OpenID Connect (OIDC) for enterprise SSO integration. Users authenticated through SSO are automatically provisioned with a default role that can be adjusted by team admins after their first login.
Why teams choose this
Built for performance, reliability, and developer experience.
Role-Based Access
Admin and Member roles at the organization level, powered by Clerk.
Team Invitations
Invite by email with role assignment. Pending invites are tracked.
Organization Scope
Team members have access to all projects within the organization.
SSO Support
Enterprise SSO with SAML and OIDC via Clerk identity platform.
Team management use cases
Enterprise teams
Assign different roles across departments — marketing edits rules, engineering deploys, and management reviews via read-only access.
Agency multi-client
Create separate organizations for each client so teams can manage their own redirects independently.
Access control
Use Admin and Member roles to control who can manage organization settings versus who works on redirect rules.
Contractor access
Invite contractors with time-limited Editor access to specific projects, then revoke access when their engagement ends.
How we compare
See how Redirections compares to alternatives.
Secure collaboration for redirect infrastructure
The role model provides two levels of access. Admins have full access including team management, billing, and organization settings. Members can create and manage redirect rules, trigger deployments, and view analytics across all projects in the organization.
Team members are scoped at the organization level — they have access to all projects within the organization. This keeps the access model simple and predictable. For agencies managing multiple clients, separate organizations provide natural isolation between client data.
All team actions are logged in the audit trail with full user attribution. Combined with the RBAC model, this gives you a complete picture of who has access to what and what actions they have taken. Team activity is also visible on the project dashboard, so administrators can monitor collaboration patterns.
Related Articles
Architecting Zero-Downtime Site Migrations: A Strategic DevOps Playbook
Infrastructure-led site migrations with edge traffic control and SEO-preserving redirect maps.
10-Step Website Migration Checklist for Zero SEO Loss
A comprehensive technical playbook for executing website migrations with zero downtime.
Related features
Explore more capabilities that work great together.
Collaborate with your team
Invite your team and assign roles in minutes. Free tier includes up to 3 members.
No credit card required · Free tier available