> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/getting-started/settings-and-configuration.md). # Settings and Configuration Settings on ENAPI are grouped by scope: what affects only you, what affects your whole organization, and what changes how ENAPI's products behave for your organization. Click **Settings** at the bottom of the sidebar to open the settings page.

Settings overview.

### User Settings — just you Personal settings that affect only your own account. * **Profile.** Name, email, password. * **Notifications.** Choose which platform events send you an email — new offers received, handshake status changes, CDR Inbox digests, and more. ### Organization Settings — your whole company Company-wide settings. Changes here affect everyone on your team. * **Business Details.** Your organization's brand name, legal name, registered address, VAT ID, and country. If you operate under multiple legal entities — for example, separate subsidiaries per country — you can configure each one here with its own banking details (IBAN/BIC) and assign it to the relevant roaming agreements and invoices. * **Team.** Your colleagues with ENAPI portal accounts. Invite new members and manage existing ones. * **Contacts.** People at your organization involved in your roaming relationships who don't need portal access — a contract signatory, a billing contact, a technical escalation. Each contact carries one or more role tags (legal, billing, general, technical inquiries) so partners know who to reach for what. Use the Hidden toggle to keep a contact internal; otherwise the contact is shared with your roaming partners and may appear on contracts and invoices ### Product Settings — how ENAPI works for you Configuration that controls how ENAPI's core products behave for your organization. * **Roaming Settings.** Your OCPI handshakes (see [Set up your OCPI Handshake with ENAPI](/getting-started/set-up-your-ocpi-handshake-with-enapi.md)), contract templates for outgoing roaming offers, and — for CPOs — data-sharing rules that control what partners can see. * **CDR Clearing.** Validation rules and thresholds ENAPI applies to every incoming CDR. See [CDR Clearing](/cdr-clearing.md). * **Invoicing.** Which legal entity issues invoices, VAT IDs, billing preferences. ### Next steps Getting Started is complete. You're ready to: * **Find partners and send your first roaming offer** → [Roaming](/roaming.md) * **Understand ENAPI’s technical details** → [Technical Documentation](/technical-documentation.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enapi.com/getting-started/settings-and-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.