Skip to content
Access control

Workspace and role-based access controls.

Membership, roles, and per-resource scoping designed around least-privilege defaults; access changes flow into the same audit trail as the work.

Evidence-grade intelligence · Human validation · Traceable decisions
Access control / evidence viewIllustrative view
layered access evaluation
Member · one workspace
Workspace membership explicitRole permits the actionResource scope allows it
Access granted, and recordedRefused, and recorded
  • WorkspaceExplicit membership
  • RolesLeast-privilege defaults
  • ResourcesScoped per project
  • ChangesRecorded in the trail
In development

SSO and SCIM provisioning are in active development.

Workspace and role-based access work today; SSO (SAML / OIDC) and SCIM provisioning for identity-provider managed teams are being built with design partners. If your team needs them, your input shapes the priority order.

The ReturnValue approach

Layered access, one shared model.

Access is reasoned about at the workspace level, refined per role, and scoped per resource. Changes flow into the audit trail rather than living in a separate admin log.

01

Workspace membership

Workspaces are the unit of access. Members are added explicitly; access does not extend across workspaces by default.

02

Role-based capability

Roles describe what a member may do rather than which screens they can open, so capability follows responsibility.

03

Per-resource scope

Projects and datasets carry their own scope, so access to one body of evidence does not imply access to the next.

How access is layered

Workspaces first, organization-wide grants last.

ReturnValue treats the workspace as the unit of access. Members are added explicitly, and a member of one workspace does not have access to another by default; broader access is an explicit grant, not a side effect of being on the team. New members start in the smallest role appropriate for the work, and anything wider is granted deliberately.

Inside a workspace, access is layered. Owner, Admin, Member, and Viewer roles carry predefined permission sets, and the role sets the baseline for what a member can see and do. Per-resource grants refine that baseline for sensitive datasets, documents, or projects that need a narrower or broader scope. Both layers are visible in the audit trail.

Admins can audit current membership, rotate access, and initiate revocation promptly when a relationship changes. For teams managing identity through an external provider, SSO (SAML and OIDC) and SCIM provisioning are in active development with design partners. Where these are needed today, we are happy to walk through the current state and the priority order.

Least-privilege defaults
New members start in the smallest role appropriate for the work. Broader access is granted explicitly and captured in the audit trail.
Scoped resources
Per-resource access layers on top of the role, so sensitive datasets can be narrower than the default role allows.
Audited access changes
Membership changes, role changes, and per-resource grants are recorded alongside the rest of the workspace activity.
Membership review
Admins can review membership and per-resource grants in one place, so periodic access reviews land on a clean view rather than a reconstructed list.
Connected investigation

Access decisions stay reviewable.

A change to membership, role, or scope is part of the same record as the investigation work it affects.

  1. 01InviteMembership explicit
  2. 02AssignRole selected
  3. 03ScopeResources bounded
  4. 04RecordChange captured
  5. 05ReviewAccess re-examined
Evidence in context

Clarity at every decision point.

Least privilege holds only when changing access is as visible as using it.

Illustrative view. Values shown are examples, not customer data.

Access layers

Least privilege
  • Workspace · explicit membership
  • Role · capability by responsibility
  • Resource · project and dataset scope
  • Audit · changes recorded
See ReturnValue in your environment

Follow your first financial signal.

Access control — Security | ReturnValue.ai