Page tree
Skip to end of metadata
Go to start of metadata


Do you use an approval workflow? If so, you might want to get familiar with the permission concept built into the app. Here are some 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. 

⠀ 


Warning

Despite these examples, we strongly advise you against setting manual permissions within spaces with an active news approval workflow. If you still decide to do so, take a look at the examples below to understand what normal app/permissions behavior in such cases might look like.


(-) Editors ⠀(-) Authors
(+) Editors ⠀(-) Authors
(+) Editors ⠀(+) Authors
The blog post creator plans news for a future release

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.

The blog post creator plans news for a future release and manually gives user X "view" permissions (in workflow space)

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).

The blog post creator plans news for a future release and manually gives user X "edit" permissions (in workflow space)

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.

The blog post creator plans news for a future release and manually gives user X "edit" permissions (before the creation of 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.

The blog post creator plans news for a future release and manually gives user X "view" and "edit" permissions (before the creation of 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.

The blog post creator plans news for a future release

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.

The blog post creator plans news for a future release and manually gives user X "view" permissions (in workflow space)

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).

The blog post creator plans news for a future release and manually gives user X "edit" permissions (in workflow space)

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.

The blog post creator plans news for a future release and manually gives user X "edit" permissions (before the creation of 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.

The blog post creator plans news for a future release and manually gives user X "view" and "edit" permissions (before the creation of 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.

The blog post creator plans news for a future release

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.

The blog post creator plans news for a future release and manually gives user X "view" permissions (in workflow space)

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).

The blog post creator plans news for a future release and manually gives user X "edit" permissions (in workflow space)

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.

The blog post creator plans news for a future release and manually gives user X "edit" permissions (before the creation of 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.

The blog post creator plans news for a future release and manually gives user X "view" and "edit" permissions (before the creation of 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.



This page was last edited on 07/23/2021.