Confluence Security

[Diego Rodriguez]

Good morning, I have several questions at Confluence level:
Understand what corresponds to security administration, all Confluence security features, and at what levels they can be shared to give visibility to pages / spaces, etc.

Use of licensing (viewing vs editing documents).

Storage: Limitations, restrictions, space availability and current contracting of the space in this cloud.

Thanks a lot

[Vero Rivas · Accepted solution]

Hi @Diego Rodriguez 

   Look at this posts, maybe can help you

   https://support.atlassian.com/confluence-cloud/docs/assign-space-permissions/

   https://confluence.atlassian.com/doc/space-permissions-overview-139521.html

   http://community.atlassian.com/t5/Confluence-questions/Confluence-Security/qaq-p/1658980

   https://confluence.atlassian.com/doc/global-permissions-overview-138709.html

Cheers

[Kirk Gould]

The Best Security to start with is give all Confluence Users Read and Comment Security for all Spaces and Pages.

From there, give Scrum Masters and Product Owners Admin capability by name for their Spaces.

From there, give users of each Space the ability to create pages, use templates, edit pages, and delete their own pages.

From there, lock down individual secret pages for super secret confidential content like pay rates and merger and acquisition plans.

Do not emulate SharePoint admin overkill where every doc has explicit named users just to view let alone edit...which is a whole nuther ball of wax.

That is like putting a combination lock on each and every room in a library and then on each shelf and each book.  It blows away the purpose of a library.

Confluence can be more of a self managed system like wikipedia when used at maximum levels.