> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/broker/getting-started/user-management.md). # User management ### Invitation The broker can invite new users to the Broker Space by going to `Settings` > `Access & notifications` > `Company access`. Enter a colleague's email address, then click `Invite`.
The invited user will receive an email from Stoïk inviting them to create their account and choose their password. ### Owners To make it easier to share information within the agency, several owners can be identified: * The account manager receives all notifications sent to the client. * The account holder receives notifications sent to the client after the contract is signed. * The payment manager receives alerts related to the client's unpaid invoices. * The claims manager receives alerts related to the client's claims. ### Roles Several roles exist for users on the Broker Space: * "Admin" users have access to the entire Broker Space and receive all transactional emails sent by Stoïk. * "Member" users do **not have access** to: * the `Billing` tab * data exports from the `Prospects`, `Clients`, and `Billing` tabs * signing the co-brokerage agreement, available from the `Settings` tab By default, all users are "Admin". --- # 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.stoik.io/broker/getting-started/user-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.