The platform
Workspace and roles
People, roles, connectors, rights identity, and how workspaces stay separate.
A workspace holds your catalogues, your people and your settings. Everything in Record is scoped to one, and no query crosses that boundary.
People and roles#
Three roles, set per person in Settings, then Members.
| Role | Can |
|---|---|
| Owner | Everything, including billing and removing the workspace. |
| Admin | Manage members, connectors, destinations and API keys. |
| Member | Work on catalogues: upload, correct, enrich and export. |
Invite by email. An invited person joins the workspace they were invited to and sees nothing outside it.
What you configure#
Settings carries the whole surface:
| Section | Sets |
|---|---|
| Destinations | Which societies you register with. Switching one off removes it from readiness and exports. |
| API keys | Keys for the Catalogue Ingest API. See Get your Record API key. |
| Connectors | Dropbox, for a folder we keep in step with your catalogue. |
| Rights identity | Your publisher names, IPIs and PRO affiliations, used to decide what you control. |
| Members | People and roles. |
| Usage and billing | What you have used and what you pay. |
| Appearance | Theme and interface font, including a dyslexia-friendly face. |
| Security | Sessions and sign-in. |
Why rights identity matters#
Your rights identity is how Record decides which writers and publishers you control, and control decides what goes into a registration.
Get it wrong and one of two things happens. We leave works you own out of an export. Or we claim works you do not own on your behalf. The second is worse, and harder to undo.
Set your publisher names, their IPIs and their PRO affiliations before your first export.
Data isolation#
- Every catalogue and work query filters by workspace. This is enforced at the API boundary, not left to a caller to remember.
- Reference data is shared on purpose. A writer's IPI is a universal fact, not yours or anyone's, so the identity caches are common to all workspaces. Your catalogue data is not.
- An API key is bound to one workspace. It cannot read or write another.
Connectors#
Dropbox is the connector that ships today. Point it at a folder, and we import catalogue deliveries from it. It is useful when a client keeps a folder up to date and you would rather not re-upload by hand.