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

Option to have different Groups for different Entry types #114

Open
engram-design opened this issue May 15, 2020 · 5 comments
Open

Option to have different Groups for different Entry types #114

engram-design opened this issue May 15, 2020 · 5 comments

Comments

@engram-design
Copy link
Member

Having the option to have different Groups as Editor and Publisher for different Entry types would be a big advantage.

@dcplebranch
Copy link

dcplebranch commented Dec 17, 2020

I would like to second this suggestion!

By the way, for anyone trying to do this currently, I have a workaround... although it's not perfect

Create Editor and Publisher groups, but don't give them rights to any specific entry types. Just give them rights to CP and Publishers should be able to see Workflow.

Then create pagesEditor and pagesPublisher. These will have the rights to edit / publish pages entries. (assuming that is one of your entry types)

Do the same with your second entry type, for example: productEditor and productPublisher.

Now assign each user a combination of editor + pagesEditor in order for them to be an editor for pages entries.
publisher + pagesPublisher for publisher of pages entries
editor + productEditor for editor of product entries
publisher + productPublisher for publisher of product entries.

It KIND of works... except I think notifications still get sent out to all publishers (i think?) And the workflow submissions lists all submissions instead of only ones each publisher has rights to.

But I hope this helps someone!

@green17
Copy link

green17 commented May 25, 2022

We could really do with this too.

@taylordaughtry
Copy link

@engram-design Hi! Is this still being considered? I'll +1 this request if so; it'd be of significant benefit to a current project!

@engram-design
Copy link
Member Author

Yep, still on the cards @taylordaughtry but no ETA.

@engram-design
Copy link
Member Author

Related #16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants