Permissions before go live

(Oliver Kass) #1

Hi folks,

 

Hopefully quite a simple one but what's the most efficient way of granting permissions for users other than sys admin to view a site before go live? We have a number of Edit+ and Backend users who I'd like to be able to access the site to review content before go live.

 

At the moment I'm just getting blank pages for non sys admins. I thought giving a user group write permissions to the site and granting public read access to the design files etc might work but no joy so far. 

 

Public user permissions are currently denied for the site content. Everything is still in under construction status.

 

Thanks

 

Oli

(Marcus Fong) #2

Blank pages? That doesn’t sound right… a user who doesn’t have permissions to view a page should normally get the Matrix login screen. Write permissions are normally all you’d need to view a page in Under Construction status.

Are these “blank pages” completely blank (i.e. View Source shows no HTML content at all), or are you getting HTML but with missing design/content elements? If the user has read access to the page itself but not to other assets the page includes, then those assets will be missing.

(Oliver Kass) #3

Yeah it seems only the barest bones of the parse file are displaying in view source. So it's maybe the paint layouts / nested content permissions then...if these are unpublished do users need write permissions to view these?

 

I'm a little confused...

(Oliver Kass) #4

Is it perhaps easier to make the design and other non-content assets live?

(Nic Hubbard) #5

Is it perhaps easier to make the design and other non-content assets live?

 

Yes, you need to make all design areas of your parse file live including all customizations.

(Tim Davison) #6

If I'm reading the question right, you also want to give access to some people tp 'preview' access to the content as well.  In other words, allow people who are not authors to see the draft content.

 

To make a preview account we do the following:

1> Create a 'User' account 

2> Place preview account in authors user group (assuming this will give at least Write access to the relevant page), or assign Write access manually.

 

Preview user needs to have Write access so they can see the draft content - otherwise they just see the Live version, or if not Live yet they see...not much.

 

The user type being 'User' prevents the preview account from being able to make any changes (they cannot access _edit or _admin areas).

 

So they can literally see but not touch.

(Oliver Kass) #7

Thanks guys, I'm gonna go with what Nick said as I think it's the unpublished design assets, asset listings, paint layouts etc that are causing issues.

 

I guess you could give users write permissions for these under construction assets but seems a little over the top just so they can see some content on the page...

(Kequi) #8

We have in the past used design based keywords on the parse file to lock down access to a single IP address (only works if you have a fixed IP of course).

 

Meaning only visitors from that IP would be able to see the site (anyone else sees an "access denied" message)

 

It was the only way we could allow them to register / login / browse pages and content with different permissions.

 

 

Once you've got the IP lockdown working you can just make the whole site live.

 

I don't know how secure that method is but it worked OK for what we needed.