Super-Admin (Platform)

1. 1

   Click 'Create Operator'

   Opens the operator onboarding form.

2. 2

   Fill in basic details

   Name: The operator's business name. Slug: URL-safe identifier (e.g., 'lucky-bet'). Brand Name: Display name shown to players.

3. 3

   Configure domains

   Add the operator's custom domain(s) (e.g., luckybet.com). These are used for tenant resolution — when a player visits luckybet.com, they see this operator's branded experience.

4. 4

   Set defaults

   Default currency, primary brand color, and revenue share percentage.

5. 5

   Create initial admin

   Provide an email address for the operator's first admin user. They will receive login credentials.

6. 6

   Save and configure

   After creation, navigate to the operator detail page to configure integrations, payment providers, and feature flags.

Click an operator row to view its comprehensive detail page with six tabs:

• Overview — Operator info, current status, headline metrics (users, bets, revenue)
• Status — Change operator status:
  • active — Full operational access
  • trial — Limited trial period
  • suspended — Access blocked, players see 503
  • deactivated — Permanently deactivated
• Admins — Admin users assigned to this operator. Add new admins, change roles, or remove access.
• Domains— Custom domains, SSL status, and DNS configuration. Players access the operator's site through these domains.
• Billing — Revenue share percentage, transaction volume, calculated fees, and invoice history.
• Integrations — Connected services: payment providers, sportsbook feeds, casino providers, analytics tools. Configure per-operator credentials and settings.

Before connecting any custom domain, the operator must have their domain on Cloudflare. Here is what the operator needs to do on their end:

1. 1

   Create a Cloudflare account

   If the operator doesn't already have one, they need to sign up at cloudflare.com.

2. 2

   Add their domain to Cloudflare

   In the Cloudflare dashboard, click 'Add a Site' and enter the domain (e.g., luckybet.com). Cloudflare will scan existing DNS records.

3. 3

   Update nameservers at the registrar

   Cloudflare will provide two nameservers (e.g., rustam.ns.cloudflare.com and sky.ns.cloudflare.com). The operator must update their domain registrar (GoDaddy, Namecheap, etc.) to point to these Cloudflare nameservers. This can take up to 24 hours to propagate.

4. 4

   Generate a Cloudflare API Token

   In Cloudflare Dashboard: go to My Profile > API Tokens > Create Token. Use the 'Edit zone DNS' template or create a custom token with Zone:DNS:Edit and Zone:Zone:Read permissions for the specific domain. Copy the generated token — it will only be shown once.

Once the operator has their Cloudflare API token, a super-admin saves it in the Puntra admin panel:

1. 1

   Navigate to the operator's detail page

   Go to Platform > Operators, click the operator, then go to the Domains tab.

2. 2

   Enter the Cloudflare API Token

   In the Cloudflare configuration section, paste the operator's API token. Optionally provide the Cloudflare Account ID (found in the Cloudflare Dashboard under the domain's Overview page, right sidebar).

3. 3

   Save and verify

   Click 'Save'. The system automatically verifies the token with Cloudflare's API. If the token is valid and active, it will be encrypted and stored securely. If verification fails, you'll see an error — double-check the token was copied correctly.

With the Cloudflare token saved, you can now add custom domains:

1. 1

   Go to the Domains tab

   On the operator's detail page, click the Domains tab. You'll see existing domains (including auto-generated .puntra.io subdomains).

2. 2

   Select domain type

   Choose 'Player Site' for the player-facing website (e.g., luckybet.com) or 'Admin Panel' for the admin dashboard (e.g., admin.luckybet.com).

3. 3

   Enter the domain name

   Type the full domain (e.g., luckybet.com or bet.luckybet.com). The system strips any protocol (https://) automatically. The domain must contain at least one dot and use only lowercase letters, numbers, and hyphens.

4. 4

   Click 'Add Domain'

   The system validates the domain, checks it isn't already used by another operator, and registers it. If Cloudflare is configured, DNS records are created automatically (see below).

When the Cloudflare API token is configured, the system automatically creates the required DNS records when you add a domain. No manual DNS configuration needed.

The system creates the following CNAME records via the Cloudflare API:

If the Cloudflare token is not configured (or the operator prefers to manage DNS themselves), they must manually add DNS records:

1. 1

   Copy the CNAME target

   The Domains page shows a blue info box with the CNAME target: ghs.googlehosted.com. Click the copy button to copy it to clipboard.

2. 2

   Open the DNS provider dashboard

   Go to the operator's Cloudflare dashboard (or wherever DNS is managed) and navigate to the DNS Records section.

3. 3

   Create CNAME records

   Add a CNAME record: Name = the domain (e.g., @ for root or the subdomain), Target = ghs.googlehosted.com. For player sites, also add a www CNAME. Set Proxy Status to 'DNS only' (grey cloud). TTL can be Auto.

4. 4

   Wait for propagation

   DNS changes typically propagate within minutes but can take up to 24 hours. SSL will be provisioned automatically once DNS resolves correctly.

After adding a domain, the SSL certificate is provisioned automatically by Google Cloud Run. The Domains tab shows the current status for each domain:

The Domains tab displays all configured domains with their type and SSL status:

• Type badges — Color-coded: Test (auto-generated .puntra.io), Player, Admin
• External link— Click to open the domain in a new tab to verify it's working
• Delete — Remove a custom domain. The system immediately invalidates caches (domain stops working right away) and automatically deletes the Cloudflare DNS records in the background if the token is configured.

1. 1

   Click 'Create Admin'

   Opens the admin creation form.

2. 2

   Set credentials

   Username, email, and temporary password. The admin will be required to change their password on first login.

3. 3

   Assign a role

   Select from system roles (super_admin, operator_admin) or custom roles you've created.

4. 4

   Assign to operators

   For operator-level admins, select which operator(s) they can access.

5. 5

   Enforce 2FA

   Toggle whether 2FA is required for this admin account.

1. 1

   Click 'Create Role'

   Opens the role creation form.

2. 2

   Name the role

   Provide a name (e.g., 'finance_manager'), display name ('Finance Manager'), and description.

3. 3

   Set permissions

   Use the permission grid to toggle access. Rows are resources (admin_users, withdrawals, bonuses, etc.) and columns are actions (read, create, update, delete, approve, execute).

4. 4

   Save

   The role is immediately available for assignment to admin users.