Roles that fit how your team actually works.
Three built-in roles aren't enough for a real organization. AnchorMark lets you define custom user groups, pick capabilities from a published catalog, and apply them per project so access matches responsibility.
Why this hurts today
QA leads need approval rights without admin power. Contractors need to triage but not change billing. Hard-coded admin/member/reviewer roles force you to over-grant access to anyone who needs to do real work — which is exactly the kind of permission sprawl your security team flags in every review.
What AnchorMark does
Custom user groups assemble exactly the capabilities a team needs from the permissions catalog. Group membership flows into project shares and SCIM provisioning so identity stays the source of truth. Every assignment is recorded in the audit log, and per-project group scopes mean the same person can be an approver on one project and a read-only reviewer on another.
Capabilities
What you get when you turn this on.
Permission catalog
Custom groups
Project-scoped roles
Immutable audit log
SCIM-driven membership
Capability discovery
Frequently asked questions
Can SCIM groups map to AnchorMark groups?
Are there per-plan limits on custom groups?
What capabilities can I assign?
Can a person belong to multiple groups?
How is this different from a normal admin/member/reviewer split?
How do I prove to an auditor who had access to what?
Keep exploring
Share projects internally with users or groups, externally with partner organizations, or publicly with magic-link guests — without giving anyone more access than they need.
Enterprise sign-on with SAML and OIDC, plus SCIM provisioning to keep teams in lockstep with your identity provider.
Tenant-first architecture, encrypted storage, and audit logs built for modern web teams.
Ship faster with feedback that already has the receipts.
Start a 14-day trial of the Team plan — no credit card required.