Concepts
Users, services, and API keys
Understand the three kinds of identity in Verentis and when to use each one.
An identity is a person or thing that can receive access in Verentis.
Verentis has three identity types: users, services, and API keys. They all receive access through roles, permissions, and grants.
User
A user is a person who signs in through an identity provider.
Use a user identity for humans. For example, use users for teammates who open Verentis in a browser, manage content, invite people, or change settings.
Service
A service is a non-person identity for software or automation.
Use a service when another system needs to act on your behalf with its own controllable permissions.
For example, you might create a service for a publishing workflow that uploads approved content to a workspace. The service can have only the access that workflow needs.
API key
An API key is a secret credential. Think of it like a long password for a script or tool.
Use an API key for quick scripts and simple integrations that need to call Verentis without a person signing in.
Keep API keys safe. Set an expiry date when you can. If a key is no longer needed, remove it.
Quick comparison
| Identity type | What it represents | How it signs in | How it gets permissions | Typical use |
|---|---|---|---|---|
| User | A person | Through an identity provider | Roles and grants | A teammate using Verentis in a browser |
| Service | Software or automation | As a non-person identity | Roles and grants | A workflow, system, or integration with controlled access |
| API key | A secret credential for a script or tool | By sending the secret key | Roles and grants | A quick script or simple integration |
Choosing the right type
Use a user when a human is doing the work.
Use a service when a system needs its own identity and permissions.
Use an API key when a script or tool needs a simple secret credential. Treat the key like a password.
Access works the same way
Users, services, and API keys can all receive roles or individual permissions. Learn more in Roles and permissions.