Administration
Use owner-scoped configuration and reviewed administrative operations without treating chat confirmation as Studio approval.
Administrative access is optional and belongs to owner accounts. A website editing credential does not automatically receive it. Select the required group under Settings → Connections → Additional access.
Match the grant to the task
| Grant | Use |
|---|---|
| Manage configuration | Read supported settings, change configuration and write provider or mail credentials |
| Send email | Run explicit mail tests or permitted notification sends |
| Manage prompt overrides | Read and change supported custom instructions |
| Manage diagnostic history | Read bounded redacted diagnostics and manage permitted history |
| Manage team | Prepare exact account changes for owner approval |
| Manage connections | Prepare credential changes for owner approval |
| Manage updates | Inspect and prepare supported installation updates |
| Prepare resets | Review site or installation reset effects |
Some configuration changes take effect immediately. Do not treat an administrative write as a website draft edit. Secret configuration values are write-only where the service supports them; a settings read is not a way to recover stored provider keys.
Approval happens in Studio
Team, credential, update and reset workflows retain the exact proposed intent for a separate owner decision. The owner reviews and approves it in Studio. A client saying “the user approved” or a confirmation in chat does not replace that step.
The approval belongs to that review and digest. If the proposed change or relevant state changes, obtain a new review rather than reusing an old approval. The owner initially enables connections and completes private workspace activation in Studio.
Updates and resets
Uploading an update package stages inert files; it does not activate the package. ZIP updates do not require shell commands. Git updates depend on explicit hosting support. Review the selected package and effects before owner approval, then continue the retained operation as instructed.
A site reset and a factory reset are different operations. The client can inspect and prepare the factory-reset review, but completion requires the owner in Studio. Read the preserved and deleted paths rather than inferring them from the word “reset.”
Recover an interrupted operation
Retain the operation ID and inspect its status. If recovery is required, use the provided recovery path or owner controls in Studio. Do not remove reservation files, reset the database or delete safety archives to force the next write through.
Diagnostics are bounded and redacted. They do not establish that the host is secure or that every third-party dependency is healthy. Review your host’s access configuration independently, especially when granting trusted PHP editing.
Found a mistake in these instructions? Open an issue.
Download VoxelSite