Administration and Troubleshooting
Administration depends on your role
Studio shows administrative pages to users with the appropriate Studio role. Backend privileges still determine which actions succeed. An organization administrator manages authorized resources in their organization; platform-wide service administration is handled by Gnok. The person who creates an organization is its first administrator.
Depending on your access, administration includes users and roles, warehouses and resource monitors, models and vector indexes, AI governance, and activity or audit views. Use least-privilege grants and check which organization you're signed in to before changing access.
Add members
An organization administrator adds members in Studio under Security → Users, then sends each person an invitation or their sign-in details. Members sign in at studio.gnok.io/login with the organization's sign-in name and their own email. A member who sees "Your account doesn't have access to Gnok Studio" needs Studio access granted by an administrator. Administrators must use a second factor; see account access.
AI and background workloads
AI features (AISQL functions, RAG, ASK/SUGGEST, and dashboard AI) are off for an organization until an organization administrator, in Studio under Operations → AI Governance, saves a monthly token budget as Available and enables a rollout policy (provider, model, operations, egress and retention approvals). Review the policy before using real data. Background feature refreshes and learning jobs use a service identity scoped to your organization with resource-specific grants. Creating the identity does not give it unrestricted table access.
See AI & ML availability and user lifecycle.
Usage and query history
Use History to investigate query outcomes, and Usage or the relevant warehouse views to inspect consumption. Account pricing and entitlements come from your commercial terms, not example values in a query result. See billing and usage.
When something fails
| Symptom | First step |
|---|---|
| Cannot sign in | Check the organization's sign-in name, your email, email verification, and your second factor; use Forgot password? if needed. See account access. |
| No connections | Check the Connections page and ask for provisioning assistance. |
| Table or model missing | Verify the connection, catalog/schema context, and object grants. |
| Shared tutorial looks outdated | Save edits, close its draft tab, and reopen the shared template. |
| Internal error with a reference | Record the reference and timestamp, and email them to support@gnok.io. |
| A write was interrupted | Check history and target state before retrying. |
| AI or background operation denied | Check Operations → AI Governance (budget and rollout policy) and the execution identity's grants. |
Email support@gnok.io with sanitized SQL, the expected result, the actual result, and the query/error reference. Customers do not need server shell access or internal service tokens to report an issue. See troubleshooting.