GoodData
Org-level connection
GoodData is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
Works with GoodData Cloud and GoodData.CN (self-hosted). Legacy GoodData Platform is not supported.
Sign in to your GoodData tenant as an organization admin. Confirm the host in your browser address bar (e.g. acme.cloud.gooddata.com or your self-hosted CN host).
(Recommended) Create a dedicated service user for On Belay with the minimum workspace roles needed (VIEW or ANALYZE for read-only agent use cases). Settings → Users → Invite. Tokens inherit the issuing user's permissions.
Sign in as that service user, then go to Settings → Developer → "Personal access tokens" → Manage → + Create.
Name the token "On Belay" and click Create. Copy the token from the dialog — it is displayed only once.
Paste:
• GoodData Host: your full host (e.g. acme.cloud.gooddata.com — no scheme, no trailing slash)
• API Token: the value from step 4
Non-admin service users may need 'organization.SELF_CREATE_TOKEN' granted by an org admin before they can mint tokens.
Ready to connect?
Sign in to On Belay and open the Integrations page to add GoodData.
Permissions (scopes)
These are the data scopes On Belay can be granted for GoodData. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
workspaces:read | Read workspaces | Read only |
analytics:read | Read dashboards/metrics | Read only |
analytics:execute | Execute analytics (AFM) | Read only |
datasources:read | Read data sources | Read only |
datasources:refresh | Trigger data refresh | Read / Write |
users:read | Read users and groups | Read only |
permissions:manage | Manage workspace permissions | Admin |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Connected but Claude can't access data
The key expires or stops working
Still stuck? We're happy to help.
Contact support →