Schema Designer Prerequisites

About Schema Designer Prerequisites | Before Schema Designer is accessible, verify that your team has accomplished its prerequisites.


In Schema Designer, administrators and users with permissions create, edit, and sync schemas. Schemas define the types and order of content that can display in pages, components, assets, and content units.

The following sections outline the tasks that CMS administrators and developers need to accomplish before users can complete their work in Schema Designer.

Developing Views

Schemas are developed according to the specification document and model how the content is structured. Ingeniux CMS stores schemas in RavenDB and doesn't publish them to the DSS. To format associated content, content units, and embedded components in the DSS (and in dss_preview), ASP.NET developers construct views to display schema instance content.

Developers need to understand the process of designing the XML schema, configuring schemas, creating pages, and deploying and rendering XML as HTML on an external system, such as the DSS. See Schema Definition and Developing Schemas for details about schema views.

If you are new to ASP.NET MVC development, see Building an MVC Website as a starting point.

Setting Schema Designer Permissions

CMS administrators have immediate permissions in Schema Designer. They can give any user group permissions to access Schema Designer. To set group permissions, administrators navigate to the appropriate group(s) in Administration > Users/Groups > Groups > Info tab.

For details about how administrators set group permissions, see Creating Groups.

Note: Keep in mind that specific groups can be blocked from accessing individual schemas. See Blocking Group Schema Access for details.

Required

Users need the following permission to access Administration > Schema Designer. Select the following permission:

  • Allowed to manage schemas: Users can work with schemas.

    Note: This permission item is in the Miscellaneous block.

Optional

Users may need to have other permissions in addition to the required Schema Designer permission. For example, to enable users to complete related tasks, you can assign permissions that expand the user's toolset and flexibility (e.g., access items in the Site Tree and Assets Tree). If you wish to assign responsibilities to users, you can designate specific permissions to a user group for designing schemas, another group for creating items associated with schemas, etc. Administrators can establish a workflow to process work between these groups.

See List of Group Permissions for details about all permissions. Choose permissions that best meet your team's needs.

Recommended permissions include:

Permissions on page manipulations: Assigns or removes the following block of permissions related to modifying pages.

  • Allowed to edit pages: Enables group members to edit existing pages assigned to the current user.
  • Allowed to delete pages: Enables group members to delete pages.
  • Allowed to check-in pages assigned to others: Enables group members to check in pages that are currently assigned to another user.
  • Allowed to rollback changes: Enables group members to rollback to a prior version of the page.
  • Allowed to assign pages not assigned to them to others: Enables group members to assign pages to other users, even though these pages are not currently assigned to the group members.
  • Allowed to create pages: Enables group members to create a new page via page creation rules or page types depending upon which additional permissions are selected.
  • Allowed to create new pages using page types: Enables group members to create pages by specifying the page type (as opposed to using page creation rules).
  • Allowed to check-in and check-out pages outside of workflow: Enables group members to check in or check out pages part or not part of a workflow.

Permissions on asset manipulations: Assigns or removes the following block of permissions related to asset manipulations.

  • Allowed to work with asset system: When selected, group members can access the Assets Manager.
  • Allowed to edit asset metadata: When selected, group members can edit metadata in the Assets Manager.
  • Allowed to delete assets: When selected, group members can delete assets from the Assets Manager.
  • Allowed to check in assets and asset folders assigned to others: When selected, group members can check in assets and asset folders that are assigned to other users.
  • Allowed to rollback assets: When selected, group members can rollback assets.
  • Allowed to assign assets and asset folders assigned to others: When selected, group members can assign assets and asset folders to other users.
  • Allowed to create assets: When selected, group members can create new assets.
  • Allowed to check in/check out assets and asset folders: When selected, group members can check in and check out assets and folders.

Permissions on Assets Tree manipulations: Assigns or removes the following block of permissions related to modifying objects in the Assets Tree.

  • Allowed to see the Assets Tree: Enables group members to view the Assets Tree in the CMS.
  • Allowed to manage asset folders: When selected, group members can execute tasks, such as moving an asset folder within the Assets Tree.
  • Allowed to reorder assets and folders in the assets tree that are assigned to others: Enables group members to relocate assets assigned to other users. If group members with this permission have full access to the start and end location of a given asset, they can move another user's asset to a new location in the Assets Tree.

Permissions on page content viewing and manipulations: Assigns or removes the following block of permissions related to viewing and modifying page content.

  • Allowed to edit the layout attribute on pages: Enables group members to change the default stylesheet applied to the current page.
  • Permission to edit password elements: Enables group members to edit password elements.
  • Allowed to view elements marked as “hidden” in Edit form: Enables group members to view hidden elements in the Edit form.
  • Allowed to add words to dictionary during spellcheck: Enables group members to add words to the default dictionary during a spellcheck.
  • Allowed to see Edit Form for page edit: Enables group members to access the edit form.
  • Allowed to see page history: Enables group members to see the page's workflow history information.
  • Allowed to view XML tab: Enables group members to access the XML tab to review XML for a specific page or component.
  • Allowed to embed/unembed component fields: Enables group members to embed components.

Permissions on asset content viewing and manipulations: Assigns or removes the following block of permissions related to viewing and modifying assets.

  • Allowed to edit asset file content: When selected, group members can edit assets such as text files, XML files, code, etc.
  • Allowed to see asset history: When selected, group members can view asset history.

Allowed to manage presentation content units: Users can work with content units. Usually, this right is given to administrators, who retain this permission by default, and developers.

Note: This permission item is in the Permissions on page presentations designing block.