Source: https://docs.amadalis.ai/reference/copilot/site-and-settings/ # Copilot: Site settings and structure Open **Copilot** in the site admin and describe the result you want. Use the tables below to check the requests in this area, their approval steps and their available Undo. Checked against the product’s code on 7 November 2026. Site identity, the front page, an active theme and EmDash content settings can affect the public site. Their approval cards describe the scope. A template setup can create several related objects at once; its receipt describes what its Undo covers. Content types, taxonomies, widgets, plugins and some settings expose EmDash’s own content management features through governed requests. Removing a field from a content type’s structure or plugin can have consequences beyond its visible row. Read the card before approval. In the tables, **Yes** under approval means a separate approval is required before applying the request. **Available** under Undo means the request can be reversed. The specific receipt must offer **Undo**; it can be limited by the input, later changes or the state that was saved. **No** means this request provides no automatic Undo. Reading a fact has nothing to undo. These are plain-language descriptions of requests, not text you must type exactly. Your role, configured connections and site capabilities determine which requests are available. See [How copilot requests are governed](https://docs.amadalis.ai/reference/copilot/). ## Content types Listing registered content types and reading their structure need Editor or Admin access. Structure changes, including registering a table and reordering fields or types, are offered only to Admins. Finding unregistered tables also needs Admin access. Approval is still required for the writes below. | Request | Approval | Undo | | --- | --- | --- | | Create a content type | Yes | Available | | Delete a content type | Yes | No | | Add a field to a content type | Yes | No | | Remove a field from a content type | Yes | No | | Reorder a content type’s fields | Yes | Available | | Update a content type field | Yes | Available | | Read a content type’s content structure | No | No | | List content types | No | No | | Register an existing content table as a content type | Yes | No | | Reorder content types in EmDash | Yes | Available | | Find content tables that are not registered as content types | No | No | | Update a content type | Yes | Available | ## Plugins Only Admins can use the copilot to check or change site extensions, called plugins. The copilot cannot install or update plugins. All supplied plugins are the platform’s own. Switching them off or uninstalling them is refused before an approval card or a change. Switching one on still needs approval and offers no Undo. Ask “Which plugins are on?” for a supported read. In this table, **Refused** means the request makes no change to a supplied platform plugin. | Request | Approval | Undo | | --- | --- | --- | | Switch an installed plugin off | Refused | No | | Switch an installed plugin on | Yes | None for supplied plugins | | List plugins and their status | No | No | | Read a plugin’s non-secret settings | No | No | | Change a plugin’s non-secret settings | Yes | Available | | Uninstall a plugin | Refused | No | After a saved plugin change, the receipt says if its result could not be read back. Use **Undo** when offered. A settings reset can have no Undo if its default cannot be checked. If Undo cannot read the current state before changing it, nothing is undone and you can retry. If the reversal is saved but cannot be read back, its reply says so. ## Readiness | Request | Approval | Undo | | --- | --- | --- | | Read the site’s readiness checks | No | No | ## EmDash site settings | Request | Approval | Undo | | --- | --- | --- | | Read EmDash site settings | No | No | | Change language, region and date or time formats | Yes | Available | | Change the site logo or browser icon | Yes | Available | | Change search ownership verification settings | Yes | Available | | Change site social links | Yes | Available | | Change site URL settings | Yes | Available | ## Site email Only an Admin can ask whether site email is configured or request a test to their own address. Keep credentials on the dedicated settings screen. | Request | Approval | Undo | | --- | --- | --- | | Read site email status | No | No | | Send a site email test to your own address | Yes | No | ## Site identity and setup | Request | Approval | Undo | | --- | --- | --- | | Read the capabilities available on this site | No | No | | Choose which page is the site’s front page | Yes | Available | | Change the site’s saved identity | Yes | Available | | Read a site overview | No | No | | List suitable site templates | No | No | | Read a site template’s pages, sections and setup needs | No | No | | Set up a site from a template | Yes | Available | | Undo a site setup from its receipt | Yes | No | ## Taxonomies | Request | Approval | Undo | | --- | --- | --- | | Create a taxonomy | Yes | No | | Delete a taxonomy | Yes | No | | List taxonomies | No | No | | Create a taxonomy term | No | Available | | Delete a taxonomy term | Yes | No | | Reorder taxonomy terms | No | Available | | Translate a taxonomy term | Yes | Available | | List a taxonomy term’s translations | No | No | | Update a taxonomy term | No | Available | | List terms in a taxonomy | No | No | | Update a taxonomy | Yes | Available | ## Themes | Request | Approval | Undo | | --- | --- | --- | | Activate an existing theme | Yes | Available | | Create a theme | Yes | Available | | Delete an eligible theme | Yes | Available | | Read themes and their token values | No | No | | List this site’s themes by their character | No | No | | Update a theme’s tokens or state | Yes | Available | ## Widget areas and instances An instance is one widget placed in an area. | Request | Approval | Undo | | --- | --- | --- | | Create a widget area | Yes | Available | | Delete a widget area | Yes | No | | Read a widget area | No | No | | List widget areas | No | No | | List widget components | No | No | | Create a widget instance | Yes | Available | | Delete a widget instance | Yes | No | | Reorder widgets in an area | Yes | Available | | Update a widget instance | Yes | Available | Return to [the copilot request index](https://docs.amadalis.ai/reference/copilot/). ## Your next step Choose a request that matches your task, then [ask the copilot](https://docs.amadalis.ai/copilot/copilot/). Review its proposed consequence before approving any change.