Project settings
A project's Settings page has four sections: Environment variables, General, Domains and Danger zone. Environment variables have their own page.
General
| Field | Notes |
|---|---|
| Project name | Read-only. It's part of every URL, so it can't change |
| Production URL | https://<project>.apps.<domain> |
| Created | Date and the person who created it |
| Owner | The accountable person; Transfer hands the project to someone else |
| Expiry | When the project would be archived if nobody opens it; Renew resets the clock |
Transfer ownership
The owner or an admin selects Transfer, picks a person from the directory, and confirms. The new owner is notified and the change is audited. The project moves to the new owner's place in the org tree, which also changes who sees it in scoped admin views.
POST /api/projects/q3-variance/transfer
Expiry
Projects that nobody opens are cleaned up automatically:
- After 60 days without anyone opening the app, the owner gets a nudge.
- 30 days later the project is archived.
The Settings page shows where the project is in that cycle, for example Not opened in 64 days: archived on 12 Jan unless someone opens or renews it. Opening the app counts as activity. The owner or an admin can Renew, which counts as activity, clears the nudge, and is audited. Admins can change the thresholds for the organization.
When the owner leaves
If the owner's account is disabled or removed in the directory, the project moves to their nearest enabled manager, who gets a notification to keep, transfer or archive it.
Domains
| Field | Example |
|---|---|
| Platform domain | apps.contoso.com |
| Production | q3-variance.apps.contoso.com |
| Previews | q3-variance--<deployment>.apps.contoso.com |
| Custom domain | Shows the DNS records you would create |
For a custom domain the page shows a CNAME from your domain to the project's production host and a TXT record _tc-verify.<domain> with the value tc-project=<project>.
Custom domains are marked Requires DNS on your Azure install: the page shows the records, but nothing is provisioned yet. Custom domains with managed certificates are coming soon.
Danger zone
Archive and restore
Archive stops the app and its Data API. Visitors see archived: ask the owner or IT to restore. The database, files and settings are kept; storage is read-only in the console. Restore brings everything back. Archive is the reversible option.
Delete project
Delete project removes the app, its database and files for good. You type the project name to confirm. Only the owner or an admin (an Org Admin, or a Delegated Admin whose scope covers the owner) can delete.
tc delete # asks you to type the name
tc delete --yes q3-variance # non-interactive
Over MCP, delete_project needs confirm: "<name>".
Deleting:
- withdraws pending access requests (approvers' Teams cards update and the requester is notified),
- revokes grants, including vendor-side permissions provisioned for the project,
- forgets environment variables,
- removes containers, the Data API, workers, routes and DNS, drops the database and its roles, and deletes files, bundles and images,
- writes a tombstone and a
project.deleteaudit event that outlive the project.
Every step is idempotent and retried until done; deleting twice answers alreadyDeleted. The name becomes reusable once teardown finishes (usually within seconds; until then creating it answers NAME_BEING_FREED).
There is no soft-delete window. If you might want the project back, archive it instead.
Who can change what
| Action | Owner | Developer (app role) | Org Admin | Delegated Admin (in scope) | Auditor |
|---|---|---|---|---|---|
| Env vars, redeploy | Yes | Yes | Yes | Yes | Read names only |
| Transfer, renew, archive | Yes | No | Yes | Yes | No |
| Delete | Yes | No | Yes | Yes | No |
Changes an admin makes on someone else's project are audited with their role, for example Adele Vance (Org Admin), and the console shows a banner on those pages.