Organization & Teams

Organization Hierarchy

Ocriva is structured around Organizations and Projects. An organization is the top-level container — it owns billing, storage, and team membership. Projects live inside an organization and scope the actual work: templates, document uploads, and processing history.

Organization (Your Company)
├── Billing & Credits (shared across all projects)
├── Team Members (org-wide roles and permissions)
├── Project: Invoice Processing
│   ├── Templates
│   ├── Uploads & Processing History
│   └── Project-specific settings
├── Project: Receipt Scanning
│   ├── Templates
│   ├── Uploads & Processing History
│   └── Project-specific settings
└── Project: Contract Analysis
    ├── Templates
    ├── Uploads & Processing History
    └── Project-specific settings

Each organization is fully isolated — data, billing, and storage do not cross organization boundaries. If you work with multiple companies, create a separate organization for each one.

Creating an Organization

1. Sign in to Ocriva and navigate to the Organizations page.
2. Click Create Organization.
3. Fill in the required fields:
   • Name — must be unique across the platform
   • Description — optional, helps team members understand the org's purpose
   • Industry — optional, used for analytics and recommendations
4. Click Create — you automatically become the owner.
5. A storage bucket is provisioned automatically for your organization.

Organization Settings

Navigate to Organization → General to update:

• Name — display name for the organization
• Description — internal description
• Logo — shown in the UI and on exports
• Website — optional external URL
• Location — geographic region

Navigate to Organization → Billing to manage:

• Subscription plan and limits
• Credit balance and top-ups
• Payment method (Stripe)

Navigate to Organization → Settings to configure:

• Allow Invites — enable or disable member invitations
• Max Members — cap on total org members (default: 10)
• Require Approval — new members must be approved before joining
• Default Role — role assigned to newly invited members

Team Roles

Every organization member is assigned one of four roles:

Permissions

Permissions can be customized per member beyond their default role. The table below shows the defaults:

Inviting Team Members

1. Go to Organization → People.
2. Click Invite Member.
3. Enter the member's email address.
4. Select a role: Admin, Member, or Viewer.
5. Optionally expand Permissions to customize individual permission toggles.
6. Click Send Invite — the member receives an email invitation and their status is set to pending.
7. Once the member accepts the invite, their status changes to active.

Managing Members

From Organization → People you can:

• Change role — select the member, use the role dropdown to assign a new role
• Customize permissions — click the member row to expand individual permission toggles
• Suspend a member — temporarily disables access without removing them; status becomes suspended
• Remove a member — permanently removes access; status becomes left

Projects

Projects organize work within an organization by use case. Each project has its own:

• Templates — extraction configurations specific to that project
• Uploads — documents uploaded within that project
• Processing History — results scoped to that project
• Members — a subset of org members can be assigned to specific projects

Credits are billed at the organization level and shared across all projects. There is no per-project credit budget by default.

Creating a Project

1. Go to Organization → Projects.
2. Click Create Project.
3. Enter a name and optional description.
4. Click Create — the project is created under the current organization.
5. Navigate into the project to start adding templates and uploading documents.

Organization Limits

Resource limits are determined by your subscription plan:

Best Practices

• Use descriptive names for organizations and projects (e.g., "Acme Corp — Finance" rather than "Org 1").
• Apply the principle of least privilege — assign the minimum role necessary for each team member.
• Use separate projects for distinct document types (invoices, contracts, receipts) to keep templates and processing history organized.
• Review member permissions periodically, especially after team changes.
• Maintain at least two owners per organization to avoid losing administrative access.
• Enable Require Approval if your organization handles sensitive documents and you want to control who joins.