by

When Tridion content authors can’t see a schema

Reading Time: 2 minutes

So, this is a quick one:

  • A content author can’t see a schema
  • Their group is scoped to a publication where the schema is located
  • The publication doesn’t exclude the author or the author’s group
  • You cut & paste the schema to another folder, and suddenly the content author can see it

Check your folder permissions

DXA, in particular, takes advantage of the concept of “modules” where various sites and experiences are different modules within a single application.

A module will have some combo of Admin, Developer, Editor, and Site Manager

No. Don’t check permissions at that module folder. Check permissions in each of its children. 

  • Right-click a folder
  • Click Properties
  • When a knew window opens, click the Security tab

Check and see if the content author’s group is added there.

A folder can have its own security settings

 

Today I learned:

I’ve been using and working with Tridion for 8 years and I didn’t know this until today:

If you set permissions on a folder, that isn’t a GUI setting. That’s a security setting for the folder and its contents. 

So remember kids

If all the permissions and roles check out, but the content author still can’t see a schema, there’s a solid chance it’s because of permissions on the folder the schema is in. Especially if you’ve got DXA, this might actually make a lot of sense if you’re keeping all of the schemas for all your modules in just one master publication.