> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Create a compliance profile with the wizard > Walk the New Compliance Profile wizard at /settings/compliance/profiles/new: pick the use case and country, see the documents and fields the country rules demand, create the draft, and attach it to the gated surface when it approves. # Create a Compliance Profile with the Wizard The wizard at **Settings → Compliance → Profiles → New** is the guided way to create a compliance profile. It walks you through naming the profile, picking the use case and country, and showing the exact documents and fields the country's rules demand — then creates the profile as a `draft` you fill and submit. This page covers creating the profile; what a profile unlocks and the order to activate a posture are on [Assemble your tenant's compliance posture](/guides/compliance-profiles-assemble), and the full endpoint surface is on [Compliance profiles API](/api-reference/endpoints/compliance). The wizard documents the tenant-owned controls only: the packet you build and the posture it opens are yours to choose. Orbit runs the review lifecycle and the surface gates; the carrier or regulator approves the packet itself. *** ## The route and the four steps The wizard lives at **`/settings/compliance/profiles/new`**, and it is reachable from **Settings → Compliance → Profiles** via the row action. It renders a single page with two panels the whole way: * **Left panel** — the form for the profile you're creating. * **Right panel** — "What you will need": the live documents and fields the use case and country demand, fetched automatically. Nothing below is a surprise the first time you submit. Work through it in this order. The first three steps are all inside the wizard; the fourth is the hand-off to the surface you want to open. 1. **Name the bundle.** Give it a name your team will recognize (`DE business KYC packet`, `US 10DLC brand`). The name is required; a new profile always starts as a `draft`. 2. **Country/vertical pre-fill.** Pick the use case from the driven list — only use cases with a real submission path in the [registry](/api-reference/endpoints/compliance) are selectable; anything tagged **Coming soon** is an explicit readiness check, and anything handled on a different surface (for example US Toll-Free Verification, which is per-number) shows a deep-link instead of a dead end. If the use case is per-market, pick the country from the live coverage list — the list only ever contains the countries Orbit's DID providers actually carry. Turn on **Multiple countries** when the same packet backs several regulated markets: the fields below fan the selection out into a per-country submission set, and you upload the documents once. 3. **Document collection and the country-rule gates.** The right panel is the checklist your chosen country and use case apply: the document roles (`certificate_of_incorporation`, `proof_of_address`, `authorized_contact`…) and the named data fields the country rule names. Read it before you create, and collect the pieces that are marked required — the rule gates submission the moment it goes to review. When the country rules don't name a packet at all (a use case with no required documents or fields) the panel says so and the wizard warns that an empty combination can't be graded; pick the use case and country you actually want to register first. The per-market demands themselves are documented on [Country Compliance Requirements](/compliance/country-requirements). 4. **Review and create.** The wizard blocks the Create button until the name is filled, the country selection resolves to a real covered country, and the chosen use case isn't one that no provider can serve — so a doomed draft never leaves the page. Click **Create**; the profile is saved as `draft`, the drafts list refreshes, and you land on the profile detail page, where you attach the documents it collected and move **Submit for review** when the packet is complete. Only an `approved` profile opens the gated surface the use case names; the lifecycle and every error the flow can surface are on [Compliance profile lifecycle errors](/compliance/compliance-profile-lifecycle-errors). The wizard is a draft-creator, not a registrant — nothing goes to a carrier until you open the profile and submit. A profile that never gets submitted never opens its surface, and a profile whose review rejects lands back in an editable state; the re-submission path is covered on [Troubleshoot a pending number or Sender ID](/compliance/troubleshooting-pending-gated-surfaces). *** ## Hand-off to the surface that needs the profile The wizard's fourth step is only the creating half of the loop; a profile does nothing until you wire it to a surface. The approved profile's id is the one every attach-by-id endpoint expects: * **Phone number purchase** — buy the number from **Numbers**, then run `POST /api/v1/numbers/:id/attach-compliance-profile` with the profile id when the purchase gate asks for it. * **Alphanumeric Sender ID** — register the sender on **Settings → Compliance → Sender IDs**, then attach the profile to the sender when the country's registration flow for that sender type demands it. * **US 10DLC brand or campaign** — on **Settings → Compliance → Brand identity**, create the brand or campaign, then attach the brand profile the campaign references. * **India (TRAI DLT)** — register the sender exactly as above, and pair the profile with the DLT artifacts the corridor demands: principal entity, headers, and templates, which Orbit records under [DLT-India Onboarding](/compliance/dlt-india). A profile never attaches by itself — every surface's gate names the profile it wants, and the profile stays a reusable packet you own. Reuse rules and rotation are on [Assemble a Shared Compliance Profile Across Gated Surfaces](/compliance/compliance-profile-assembly). *** ## Two same-wizard examples: US 10DLC vs India DLT The wizard's right panel changes with the use case and country — the same four steps produce very different checklists. * **US 10DLC brand.** Pick **10DLC brand (US)**: this use case needs no per-market country gate, so the checklist is the brand identity packet the Campaign Registry grades (legal entity, address, contact data, and the fields the brand form names) — no country rule document chain, and the review is The Campaign Registry's. Pair it with the campaign profile when the traffic starts; both profiles attach to the same brand identity and traffic degrades until both clear. * **India — DLT over the sender-ID corridor.** Pick **SMS alphanumeric sender** with country **IN**: the right panel collects the identity packet the corridor asks for, and India adds its own registration scheme on top — the TRAI DLT principal entity, headers, and content templates must exist before traffic delivers. Register them on a DLT portal, record the resulting ids via [DLT-India Onboarding](/compliance/dlt-india), then register the sender with the profile attached. A sender without a live DLT entity + header stays at the corridor's pending gate until both sides clear. The same flow for every other corridor: read the country rule, let the wizard state what the rule demands, create the draft, and hand the approved profile off to the surface that gates on it. *** ## Where this fits in the posture Creating a profile is one step of the day-one assembly on [Assemble your tenant's compliance posture](/guides/compliance-profiles-assemble) — read the country rules first, run the wizard to create the profile, submit, then attach the approved profile to the surface it opens. The wizard's checklist matches the country rule's packet, and the surface gate only relaxes when the review approves. Deep references: the packet itself is documented field-by-field on [KYC Documents & the Compliance-Profile Lifecycle](/compliance/documents-kyc), and the reuse/rotation pattern is on [Assemble a Shared Compliance Profile Across Gated Surfaces](/compliance/compliance-profile-assembly).