Administer access & settings
The Settings group is administrator-only — it holds the credentials and configuration that let other systems talk to MonetizeIt, plus your environments. (Admin)
Users, roles and seats
Section titled “Users, roles and seats”People, roles and seats are covered in their own guide — Set up your account & team. In short: Customers → Users, assign one of the four roles, mind the administrator-seat cap.
API credentials
Section titled “API credentials”Settings → API credentials is where you register the OAuth/OIDC clients your own code authenticates as. For each client you set a type (public or confidential), its grant types, scopes and redirect URIs.
- Create a client, then copy the client ID. For a confidential client the secret is shown once on creation — copy it then; if it’s lost, Rotate Secret to issue a new one.
- Enable/Disable or Delete a client to cut off access.
- Platform-managed clients (the portals and internal callers) are read-only — you can see them but not edit them.
This is the portal side of Authentication for developers — the scopes you grant here are exactly what the API enforces.
Integrations
Section titled “Integrations”Settings → Integrations issues OAuth credentials for off-the-shelf tools (e.g. Zapier) rather than your own code. Create a credential, Rotate Secret, and Enable/Disable as needed. It’s the same idea as API credentials, scoped to a named integration.
Webhooks
Section titled “Webhooks”Settings → Webhooks is where you subscribe an endpoint to events. Create a subscription with its event types, receiver URL, callback scopes and signing secret; Test it, Rotate Secret, and inspect and requeue failed deliveries. The event catalogue and signature-verification details are in the developer reference — Webhook events; building a receiver is covered in Receiving webhooks.
Environments
Section titled “Environments”Settings → Environments lists the environments under your account — production and an optional sandbox — and lets you provision a sandbox (one per account, once production exists). Model and rehearse in the sandbox; promote the catalog with Catalog transfer.
Catalog transfer
Section titled “Catalog transfer”Settings → Catalog transfer exports and imports catalog data as JSON — handy for moving a modelled catalog from sandbox to production or keeping environments in step. Export the sections you want; Import applies a file to the current environment.
Compliance
Section titled “Compliance”Administrators also have the Compliance group — Audit Log, Privacy Requests and Processing Activities. Those are covered under Security & Compliance.