Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: disable certain content types for certain users #643

Open
yolpsoftware opened this issue Aug 30, 2023 · 0 comments
Open

Enhancement: disable certain content types for certain users #643

yolpsoftware opened this issue Aug 30, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@yolpsoftware
Copy link

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:

image

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).

@yolpsoftware yolpsoftware added the enhancement New feature or request label Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant