Permanently deleting administrative objects

Editors use the next available dashboard in the content hierarchy. (For example, you delete a dashboard assigned to an editor. The editor then sees the dashboard assigned to the role, if available.) If no other dashboards are configured in the hierarchy, editors see the system-level default dashboard.

A permanently deleted site loses the ability for domain-name resolution. To avoid loss of SEO rankings, and to prevent visitors' seeing errors about domain-name resolution, add site redirects as appropriate. For details, see Adding a site redirect.

Configurations using the deleted site are no longer applicable. For example, a workflow applied to a deleted site is no longer in force.

The user's name no longer appears in various widgets, such as Recent Activity.

Editors may see an error message similar to No accessible site! (java.lang.IllegalStateException). Before permanently deleting a role, assign all associated users a different role.

Assets exit the workflow and return to draft status; they can be immediately published.

New assets—After permanently deleting a content form, roles associated with that form fall back to the default form for the underlying content type. For example, if you permanently delete a content form for articles, the roles configured for that form see the default content edit form for new articles.

Existing assets—Brightspot continues to manage existing assets using the content form used to create them, even if the content form is deleted. For example, a content form Brief for articles includes only the Main tab, and you created an article using that content form. Even after deleting Brief, the article you created continues to have only the Main tab available in the content edit form.