You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. We have different users working on different content types. Some users work on all, but most of our users just work on one of them. For example, User 1 works on blog, User 2 works on docs, but User 3 works on both. Currently, when User 1 opens the Front Matter CMS Dashboard, they always have to change the "Showing" setting to blog, such that they only see the blog items:
Describe the solution you'd like
It would be great if we could limit the content types in a local file (for example, one in the .frontmatter directory). If the file is not present, Front Matter CMS behaves as it does currently.
Describe alternatives you've considered
Maybe an alternative would be the Local Settings, but as I understand that feature, it allows us to move the configuration to local files. That means we have to duplicate the configuration: The config of blog would need to be present on both User 1 and User 3's workstation.
If we can disable a content type locally, we could keep them all together in the Team Settings (frontmatter.json).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes. We have different users working on different content types. Some users work on all, but most of our users just work on one of them. For example, User 1 works on
blog
, User 2 works ondocs
, but User 3 works on both. Currently, when User 1 opens the Front Matter CMS Dashboard, they always have to change the "Showing" setting toblog
, such that they only see theblog
items:Describe the solution you'd like
It would be great if we could limit the content types in a local file (for example, one in the
.frontmatter
directory). If the file is not present, Front Matter CMS behaves as it does currently.Describe alternatives you've considered
Maybe an alternative would be the Local Settings, but as I understand that feature, it allows us to move the configuration to local files. That means we have to duplicate the configuration: The config of
blog
would need to be present on both User 1 and User 3's workstation.If we can disable a content type locally, we could keep them all together in the Team Settings (
frontmatter.json
).The text was updated successfully, but these errors were encountered: