Projects
Projects organize work inside an organization: who can access what, and which configuration and models apply.
Organizations and projects
Every user — whether self-registered or invited — belongs to one organization.
An organization can have multiple projects. Use projects to:
- Control which users can access which workspaces
- Apply different anonymization configurations and models per project
Default project
When a user self-registers, doccape automatically creates a first project. That project becomes the organization’s default project.
A default project works like any other project, with one important difference for the REST API: you can call endpoints without a project ID in the path. In that case, the default project is used.
This applies to:
- Anonymize text —
POST /external/v1/text - Anonymize documents — default endpoints under
/external/v1/documents/…(no{projectId})
To target a specific project instead, use the project-scoped document endpoints under /external/v1/projects/{projectId}/….
Discover accessible projects
List projects visible to your current API key with GET /external/v1/projects/me. Which projects appear depends on the key scope.
Project settings
When creating a project, you can configure the following settings:
| Setting | Description |
|---|---|
| Project Template | Determines which text model labels are supported for anonymization in this project. |
| Disable document correction | When enabled, no personal data is stored. Manual correction of documents is therefore not possible. |
| Enable automatic deletion | Documents in temporary projects are deleted after the specified number of hours. |
Project Template and Disable document correction cannot be changed after the project is created.
Next steps
- Anonymize Documents — default vs project-scoped workflows
- API Keys — create a key and choose a scope