{"templateId":"openapi_docs","sharedDataIds":{"openAPIDocsStore":"oas-openapi/content-intelligence.yaml","sidebar":"sidebar-sidebars.yaml"},"props":{"definitionId":"openapi/content-intelligence.yaml","dynamicMarkdocComponents":[],"baseSlug":"/openapi/content-intelligence","seo":{"title":"Authentication","llmstxt":{"hide":false,"sections":[{"title":"Table of contents","includeFiles":["**/*"],"excludeFiles":[]}],"excludeFiles":[]},"description":"These endpoints provide authorization primitives for verifying user permissions and\nbootstrapping new user access within the Content Intelligence Platform.\n\nThe platform uses a role-based access control (RBAC) model managed by the Authorization\nservice. Roles carry named permissions, and users are assigned one or more roles either\nexplicitly or via [User Groups](#tag/User-Groups).\n\n- `has-permission` — check whether the calling user holds a specific named permission;\n  use this as a guard in custom integrations before performing sensitive operations\n- `assign-default-role` — assign the platform default role to a user, typically called\n  during user provisioning or invite acceptance flows\n\nFor fine-grained, resource-level access decisions (e.g., \"can this user access this\nspecific document?\"), see [Access Control](#tag/Access-Control).\nFor managing the roles themselves, see [Roles](#tag/Roles).\n"},"itemId":"authentication","disableAutoScroll":true,"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"api.tenovos.com","port":4000,"ipAddress":"216.73.217.51"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/openapi/content-intelligence/authentication","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}