How do I restrict access to just one collection?

I've not upgraded the live website yet, I'll have to update the development site. I just thought you might know off the top of your head - no worries - I'll update the dev site and report back.

Thanks for the reply Stephen

Hi Drew

I've updated to 2.8.10. I can't get it to work?

Here's a screenshot of my role creation screen, Under privileges I was hoping to see a section called collections with all the collections I've created listed.

I want to create a role that only has access to a collection called projects.

Thanks Drew

I can limit access to the collections, but they still show in the menu (when the restricted user is logged in), plus there's a few things that aren't working as expected.

Here's what I have.

A new role called Limited Access (this is just a test role name)

The only checkbox ticked is Log in, I'd expect everything else that isn't ticked to not show for this user. This doesn't happen?

When I login as the restricted access user, I still see parts of the website I don't want this user to have access to.

• The only privilege I selected for this user was the option to login
• I only need this user to have access to and see the projects collection - nothing else.
• How come this user can still access/see Pages and MailChimp
• The user can also see vacancies, but they can't access it. If they can't access it, why can they see it?

Hi Drew

Thanks for the reply :)

Will it ever be possible to create a user with access only to one or a handful of collections?

My use case is I've a large collection called projects, my client wants a third party to update this part of the website - but doesn't want them to have access to anything else.

I'll upgrade MailChimp app (whoops).

Hope to see the bug fixed in a future release.

Thanks again Stephen

Hi Drew

I have a client that wishes to have exactly this functionality (for effectively the same use case too). Are there any plans in the near future to create a user role that has a 'Manage Collections' permission, that can tie in to the current functionality with adding a role to the collection too (so we can restrict them to the Vacancies collection)?

Thanks.

Lee

Hi Drew

I've be asked about this from another client recently.

We'll need to have a think about access to pages. It throws up lots of questions, like where does a user get sent to when they log in!

As the login would be associated with one collection, wouldn't the user be sent to that collection?

I have the same requirement. A client needs to be able to provide user access to collections but restrict access to page editing of any sort.

As for where to send them when they log in: an empty page with "Collections" visible in the top level menu would be sufficient. It always seemed odd that Collections are a sub navigation of Pages. In many use cases Collections don't have much to do with Pages and deserve to be a top level menu item.

Hi

I have a project in mind that feels like a great fit for Perch Runway.

However, a key part of the website involves three tiers of users.

The only part of the CMS each user will need to see will be a collection (or perhaps a set of collections).

None of the users should be able to see the pages or anything else of the website.

Is this something Perch Runway 3 could do?