Share Content and API Keys

Prev Next

Users can create their own entities and API keys. Sharing is limited to the team, and key management depends on role.

Access rights on shared content

Sharing is possible only inside the team. When entities such as saved queries, monitors, or assets are shared, the recipient's access level is defined by one of two rights:

  • Can Edit (Contributor right) — a middle-level right. Users can look at, read, update, and edit the shared entity.

  • Can Manage (Administrative right) — the higher-level right, automatically granted to whoever creates an entity. It includes everything in the Edit right, plus the ability to delete the entity. Only the entity's owner can delete it.

API keys

Every user can create their own API keys. What they can see and manage beyond their own keys depends on role:

  • Owner — can view, revoke, edit, allocate API credits, and copy every API key in the organization.

  • Manager — can view, revoke, edit, and copy every API key created within their team.

  • Member — can view, edit, and copy only the keys they personally created.

Automatic email reminders are sent to the key's owner 30 days and again 7 days before a key expires. A final notice is sent once the key has expired.