Controller access to an individual site is confusing

[willguv]

I'm a controller at Essex trying to access the content for one of our sites. This is the view I'm presented with

It's not clear I need to click "Microsite administration" in the nav

Also, what would I see on this page if we had more than one site?

[stephen-cox]

Our recommendation has been that you don't access the content of a Microsite as the controller; you certainly shouldn't be editing content as a controller. I do agree that this can be confusing through.

That said there's something odd with that site. The 'Microsite administration' link should only be visible to site editor and admins, not controllers. Also the latest version displays a warning that you're logged in as a controller.

Controller view

Site admin view

[finnlewis]

@willguv I think you're on an older version of LocalGov Microsites at the moment, so maybe your specific issue will be resolved once upgraded to the current 4.x branch.

It does touch on the controller user experience though.

As Stephen mentions, we do not support a "controller" user editing content on the control site, and it would be good to make this as clear as possible, or as difficult as possible, or even prevent it from happening completelt.

The controller user should just create microsites, configure them, and add/manage users to microsites.

This does pose the question, what if I am the controller and the site content manager? Hmmm.

[ekes]

I think, it'd need a bit of working out for sure, we could now (4.x) add another context for the new permissions access calculation that alters the permissions on the control site (the only domain that hasn't got a group context) which removes all content permissions then. After that if you want the controller to have permissions when logged into all other sites, on their domains, over content it wouldn't be an issue.