Security & trust
Four roles, different responsibilities.
| Permission | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| View records | Yes | Yes | Yes | Yes |
| Create and edit records | Yes | Yes | Yes | No |
| Delete records | Yes | Yes | No | No |
| Manage members | Yes | Yes | No | No |
| Manage API keys | Yes | Yes | No | No |
| Manage billing | Yes | No | No | No |
| Delete workspace | Yes | No | No | No |
Admins can view billing. Changes to billing and workspace deletion remain with the owner.
Workspace data boundaries
Records are scoped to a workspace. Database row-level policies enforce membership boundaries, while application permissions govern the actions available to each role.
Integration access
Workspace API keys carry explicit scopes. Limit the actions a connected service can take, and revoke its key when access is no longer needed.
Activity and audit history
Record activity and agent threads help you inspect the work. Account and membership changes are recorded in an append-only audit trail.
Account deletion
Request account deletion from the app. Shared workspace records and required audit history follow the retention rules in the privacy policy.
Read the privacy policy“Working with Lineer for the past 6 months has been exceptional. Their team has shown outstanding expertise and remarkable patience as we've navigated our projects together.”
Review the controls with us
Talk through your workspace, access requirements and approval process.