> For the complete documentation index, see [llms.txt](https://lern.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lern.sunbird.org/use/developer-guide/user-and-org-service/architecture.md). # Architecture ## UserOrg Service Architecture The below diagram represents the components involved and their arrangement in **UserOrg** service.

### Flow Diagram:

* User service includes multiple operations to creating new users and search the user. * Keyclock for user authentication. * Enabled Notification feature and messaging like Email and SMS on any operations performed. * Updation of user details using jobs. * OTP Creations on user merge action. * Admin Util will do token verification. * Content service is for to register the channel and framework validation. * Userorg service will send an audit event to `{env}.telemetry.raw` topic. This event will be processed by pipeline-preprocessor(SB-Obsrv) and valid events will pushed to the audit topic to cache the user data by `user-cache-updater-v2` flink job. {% embed url="" %} User-Org Highlevel Architecture {% endembed %} --- # 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://lern.sunbird.org/use/developer-guide/user-and-org-service/architecture.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.