Customise the Anythink Dashboard
Customise your Anythink project from the Organisation Settings page — change the name, upload logos, control who can register, configure CORS, and set payment redirect URLs.
Organisation Settings
Go to Settings → Organisation to configure your project.
Name and description
Set the name and description for your project. The name appears throughout the dashboard and in system emails sent to your users.
Logos
Upload two versions of your logo:
| Logo | Use |
|---|---|
| Square logo | Dashboard favicon, compact UI areas |
| Standard logo | Dashboard header, full-width branding areas |
Logos are uploaded as files via the file uploader. Supported formats: PNG, SVG, JPEG.
User registrations
Allow Registrations controls whether new users can sign up directly to your app.
- On — anyone can create an account via
POST /auth/v1/registeror your sign-up UI - Off — new accounts can only be created by an admin (via the dashboard or API)
When registrations are on, you can set a Default Role — the role automatically assigned to every new user who signs up. This controls what they can see and do in your app from day one.
Roles and PermissionsCORS — allowed application URLs
By default, Anythink allows requests from Anythink-hosted domains and localhost. To accept requests from your own domain, add it here.
Enter the full origin (e.g. https://myapp.com). You can use wildcard subdomains: https://*.myapp.com.
Multiple URLs are supported. Changes take up to 2 minutes to propagate.
Payment redirect URLs
If you use Anythink Payments (Stripe Connect), configure where users land after a payment:
| Setting | Description |
|---|---|
| Payment success URL | Redirect here after a successful payment |
| Payment cancel URL | Redirect here if the user abandons checkout |
These URLs must be on your domain (not localhost in production).
Google Maps API key
If you use geo field types and want to display a map picker in the dashboard, enter your Google Maps API key here. Get a key from the Google Cloud Console.
Without a key, geo fields still store and return coordinates via the API — the map UI in the dashboard just won't render.