- Created by Administrator, last modified on Nov 14, 2024
Documentation's navigation
On this page
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.
⠀
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.
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.
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.
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.
☁️ Looking for a Cloud-based Intranet?
Check out Mantra, your go-to alternative to Linchpin in the Atlassian Cloud!
Mantra is your a comprehensive solution for connecting teams, making collaboration a breeze, and keeping your company's internal communication strong and streamlined - all in the cloud.
Test the intranet for Confluence Cloud now for free:
Link to this page: https://seibert.biz/len-permissions-examples