Owner
Workspace control, members, keys, and audit
Security
Control the work without slowing it down.
Keep human and agent access understandable with clear organization, app, role, and permission boundaries.
Current controls, explained plainly.
Rowkit applies the same control model whether work begins in the interface or through an agent key.
Organization isolation
Workspaces and membership resolve inside the active organization boundary.
Workspace roles
Owner, builder, editor, and viewer roles make human capabilities explicit.
Scoped keys
Agent keys bind to one app with a fixed schema and record permission set.
Audit visibility
Owners can review important schema, record, member, and API-key events.
Human roles
Give people the access their responsibility needs.
Builder
Schemas, views, and records
Editor
Read and edit records
Viewer
Read workspace data
Agent access stops at the app boundary.
Keys expose the schema and record operations granted for one app. Membership, organization settings, and audit administration stay outside that route.
TenantOrganization
ContainsWorkspace
ContainsApp
Reaches only this farScoped agent key
This page describes controls present in Rowkit today. It does not claim external compliance certification.
Build with boundaries from the start.
Create the workspace, assign the right roles, and scope every connected agent to its job.