Edit configuration in Configuration Studio

Before changing a target

Open Find a workspace → Administration → Configuration studio & governance. Verify that you have the intended tenant, an authorized author and any required independent reviewer. Identify the registered target and capture its active configuration and version or fingerprint.

Make a governed edit

1. Use Export current target for an existing registered target. Supported metadata packages can cover field overrides, module/workspace settings, registered table and field labels, list layouts, access policies, ticket notification rules, CSM playbooks, agent definitions and dashboard panels.
2. Edit the exported configuration in the cloud development workspace. Preserve the expected version or fingerprint. For a supported new target, use the format specified by its artifact type.
3. Re-seal and validate. In Configuration Studio open Metadata as code, paste the sealed JSON, and preview the change in the destination tenant.
4. Review the effective changes and protections. Save a draft and submit it for review. After approval and any required MFA step, apply using the controlled action.
5. Reopen the target. Test its intended users and at least one unaffected or denied case. Record the package and audit receipt.

CLI example

pnpm build
node scripts/configuration-code.mjs seal configuration.json > sealed.json
node scripts/configuration-code.mjs validate sealed.json
node scripts/configuration-code.mjs explain sealed.json
node scripts/configuration-code.mjs diff previous-sealed.json sealed.json

Conflict and rollback

A stale fingerprint means the baseline changed. Export the new target, reconcile the intended edits, reseal, preview again and obtain a fresh review. Use the native rollback procedure for approved packages. Review the rollback effect and verify the restored configuration and affected roles. Metadata edits affect registered configuration. Physical database changes use append-only migrations and the platform release process.