Workspace Setup
Workspace setup describes how a customer organisation is provisioned and prepared for use in Nairo.
A workspace is the tenant-scoped environment where an organisation’s users, documents, configuration and review work are managed.
What workspace setup involves
A typical workspace setup includes:
- Tenant creation and provisioning
- Workspace URL or slug configuration
- User invitations and role assignment
- Initial Library structure
- Upload of reference materials and test documents
- Selection of the first product surface to use
- Definition of the initial pilot workflow and success criteria
Nairo platform administrators manage tenant provisioning at the platform level.
Customer administrators manage users, roles, permissions and workspace materials within their own workspace.
Tenant provisioning
For a new customer organisation, Nairo provisions a tenant before users begin working in the product.
A tenant typically maps to:
- A workspace identifier
- A workspace URL or slug
- Authentication context for workspace users
- Tenant-scoped users, roles and permissions
- Tenant-scoped documents and product configuration
Users access Nairo through the relevant workspace URL or organisation context.
Access to documents, folders and product areas depends on the workspace setup and the permissions assigned to each user.
For more detail on tenant boundaries, see Tenant Isolation.
Customer admin setup
Once the workspace is active, customer administrators usually complete the first setup tasks.
These may include:
- Inviting pilot users
- Assigning roles
- Confirming who can manage users and permissions
- Creating the initial Library folder structure
- Uploading guidelines, wordings and reference documents
- Creating or reviewing initial Projects
- Confirming which Experts and Actions are available
- Defining which users will review AI-generated outputs
The exact setup depends on the customer’s pilot scope and workspace configuration.
Initial Library setup
Most workspaces start by uploading a small set of high-value materials.
Examples include:
- Underwriting guidelines
- Appetite materials
- Policy wordings
- Claims handling guidance
- Internal reference documents
- Sample document packs
- Templates or standard forms
Documents may be uploaded directly to the Library or through product surfaces such as Projects, where supported.
Uploaded documents may need to be processed before they can be used in AI-assisted review.
Customer teams should confirm that the materials uploaded are current, approved and appropriate for the intended workflow.
Choosing the first workflow
Most teams start with one focused workflow rather than enabling every product surface at once.
A good initial workflow should have:
- A clear user group
- A clear document set
- A repeatable review question
- A defined human review process
- Clear success criteria
- Low ambiguity around which materials should be used
Common starting points include:
- Underwriting review
- Policy comparison
- Claims file review
- Appetite review support
- Structured extraction across document sets
The first workflow should be narrow enough to evaluate properly.
Pilot planning
A focused pilot should define the operational scope before users begin.
| Item | Example |
|---|---|
| Team or business unit | Commercial underwriting |
| Initial workflow | Review one class of underwriting document pack |
| Product surface | Projects, Experts or Insight Table |
| Documents required | Appetite guide, standard wording, sample document packs |
| Expected users | Underwriters, team lead, admin user |
| Review process | Human review before output is used |
| Success criteria | Faster first-pass review, better document visibility, more consistent output format |
The pilot should also define what Nairo is not expected to do.
For example, Nairo should not be treated as an autonomous decision-maker, system of record, policy administration system or claims platform.
Responsibilities
Workspace setup usually involves responsibilities on both sides.
Nairo is responsible for:
- Provisioning the tenant
- Making the workspace available
- Supporting initial configuration
- Providing access to the relevant product surfaces
- Supporting the customer during pilot setup
The customer organisation is responsible for:
- Identifying pilot users
- Deciding which materials should be uploaded
- Confirming which documents are current and approved
- Assigning appropriate roles and permissions
- Defining the human review process
- Deciding how outputs should be used or retained internally
What workspace setup is not
Workspace setup does not replace the customer’s internal governance process.
It does not decide which documents are authoritative.
It does not automatically configure a complete production rollout.
It does not replace security, legal, procurement or compliance review where those are required by the customer.
It prepares the workspace so the customer can begin using Nairo in a controlled, reviewable way.
Related areas
- Users and Roles - inviting users and assigning roles
- Permissions - controlling access to workspace features and materials
- Library - uploading and organising documents
- Data Sources - understanding where materials come from
- Tenant Isolation - tenant boundaries and workspace separation
- AI Usage and Human Review - reviewing AI-generated outputs
Getting started
For a first setup, start with one workspace, one team and one workflow.
Provision the tenant, invite the pilot users, upload the minimum required materials and run one representative case before expanding the scope.