> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/operational-guidelines/user-directory-management.md). # User Directory Management User Directory Management covers invitation-based enrollment, claim assignment, group administration, claim updates, and account deactivation. Administrators perform these operations from the Authentik Admin Interface. Before performing user-management operations, verify that: * Authentik is running and accessible over HTTPS. * You have Authentik administrator access. * The appropriate OE blueprint has been applied successfully. * The enrollment flow exists. * The OE property/scope mappings are attached to the relevant OIDC provider. * SMTP is configured if invitations are sent by Authentik email. * The organization-specific values to be assigned to the user are known and have been validated. *** User Directory Management covers the operational lifecycle of users stored directly in Authentik. The procedures apply to users in either the Data Space Operator or Data Space Participant Authentik instance. The user management repository configures an enrollment flow named: ``` oe-enrollment-invitation ``` The flow requires an invitation and creates internal users through the following User Write stage: ``` oe-enrollment-invitation-write ``` The configured enrollment flow also checks for existing e-mail addresses and usernames. The repository defines the following deny messages: ``` Email already exists! Contact admin. Username already exists! Try another one. ``` The enrollment flow creates the user as active. It does not create the user in a predefined group. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.oceanenterprise.io/operational-guidelines/user-directory-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.