On this page:

Permissions explained with examples

Examples of use cases

To better understand how permissions work within Linchpin Enterprise News, we created this overview of different use cases and expected behavior as of version 2.16.4 of Linchpin Enterprise News.

(-) Editors (-) Authors

Inside the workflow space:

The creator can view and edit the blog post.

Inside the original space containing the news:

Everyone can view and edit the blog post.

Inside the workflow space:

The creator can view and edit the blog post. User X can view the blog post.

Inside the original space containing the news:

The creator can view and edit the blog post. User X can view the blog post. Others can’t view the blog post (since the visibility was limited to user X).

Inside the workflow space:

The creator and user X can view and edit the blog post.

Inside the original space containing the news:

The creator and user X can view and edit the blog post. Everyone else can still view the blog post.

Inside the workflow space:

The creator and user X can view and edit the blog post.

Inside the original space containing the news:

The creator and user X can view and edit the blog post. Everyone else can still view the blog post.

Inside the workflow space:

The creator and user X can view and edit the blog post.

Inside the original space containing the news:

The creator and user X can view and edit the blog post. Everyone else can still view the blog post.

(+) Editors (-) Authors

Inside the workflow space:

The creator and editor(s) can view and edit the blog post.

Inside the original space containing the news:

Everyone can view and edit the blog post.

Inside the workflow space:

The creator and editor(s) can view and edit the blog post. User X can view the blog post.

Inside the original space containing the news:

The creator and editor(s) can view and edit the blog post. User X can view the blog post. Everyone else can’t view the blog post (since the visibility was limited to user X).

Inside the workflow space:

The creator, editor(s) and user X can view and edit the blog post.

Inside the original space containing the news:

The creator, editor(s) and user X can view and edit the blog post. Everyone else can still view the blog post.

Inside the workflow space:

The creator, editor(s) and user X can view and edit the blog post.

Inside the original space containing the news:

The creator, editor(s) and user X can view and edit the blog post. Everyone else can still view the blog post.

Inside the workflow space:

The creator, editor(s) and user X can view and edit the blog post.

Inside the original space containing the news:

The creator, editor(s) and user X can view and edit the blog post. Everyone else can still view the blog post.

(+) Editors (+) Authors

Inside the workflow space:

The creator, editor(s) and a team of authors can view and edit the blog post.

Inside the original space containing the news:

Everyone can view and edit the blog post.

Inside the workflow space:

The creator, editor(s) and a team of authors can view and edit the blog post. User X can view the blog post.

Inside the original space containing the news:

The creator, editor(s) and a team of authors can view and edit the blog post. User X can view the blog post. Everyone else can’t view the blog post (since the visibility was limited to user X).

Inside the workflow space:

The creator, editor(s), a team of authors and user X can view and edit the blog post.

Inside the original space containing the news:

The creator, editor(s), a team of authors and user X can view and edit the blog post. Everyone else can still view the blog post.

Inside the workflow space:

The creator, editor(s), a team of authors and user X can view and edit the blog post.

Inside the original space containing the news:

The creator, editor(s), a team of authors and user X can view and edit the blog post. Everyone else can still view the blog post.

Inside the workflow space:

The creator, editor(s), a team of authors and user X can view and edit the blog post.

Inside the original space containing the news:

The creator, editor(s), a team of authors and user X can view and edit the blog post. Everyone else can still view the blog post.

Safety Guidelines

We strongly recommend the following Confluence configuration settings to avoid potential security risks:

Make sure people are not allowed to register their own accounts, especially without restriction to your domain.

If you allow anonymous access, make sure anonymous users don’t have permission to create or edit anything anywhere (pages, blogposts, comments, attachments etc. in any space).

If you configure your instance differently, you do so at your own risk.

Link to this page: https://seibert.biz/len-permissions-examples