a confluence space for six differents teams, how to deal with acess rights propely?
Asked by Francoise DUCLOS:

Hello, Guys

I need to create a confluence space for a departement composed of 6 differents teams, which are supposed to work together and which deal with internal and confidentiel documentations.

How to structure it?

How to manage rights access policy ?

in a simple way ?

Thanks for your help


Answers:
author: Gezim Shehu [Communardo]
body: Well the first question lies, if you can actually separate those? Or is it a fixed external requirement to have 1 space only?

If one space it is...

I would start with the public "subspace", which should be the easiest.

Simply create a Parent page named "Public" set no restrictions to it.

Same logic applies on other 6 individual Parent Pages

Team 1

Team 2

Team 3

Team 4

Team 5

Team 6

Each Team page would have restrictions on view and edit, based on each Teams. You can use Confluence groups for teams, so it's easier to maintain.

Cheers

comments: author: Francoise DUCLOS
body: The unique space is not a requirement, we believed that the fact to have one space would be fructfull for team collaboration. My departement is dedicated to Internet services, we work with IAD, STB, and plateforms teams, each team have "internal" and "confidential" document, but with One Space, each members of the team, could have access easily to others pages, especially pages from others teams.

I keep your answer which have been the first one donne here too; I would have to manager teams access with group, as in each child page I will have to create "autorized' pages in reading and others forbidden

Best regards


author: Gezim Shehu [Communardo]
body: Hi,

Personally I recommend spaces based on scopes. Meaning what is the space scope?

If it's for the internal team, than it should be a Team Space. If it's a public, or a collaboration space (maybe for 1 project) then it should be accessible to all relevant members.

Parent Page based permissions are a bit rudimentary, but still can work given your usecase.

One other alternative might be using excerpts? Maybe you could have some separate spaces, simply split into 2 (public, private) and the public material you could expose using excerpts.

Best Regards


author: Francoise DUCLOS
body: The space scope is to gather all the information available on a project, or on a new service Under construction. It include platform evolution documentation, STB version, IAD version, and a set of STI (technical interface sp?cifications ).

One space / for one project is too big,

I have two questions Gezim

do we have the notion of folder on COnfluence ?

How two spaces can communicate easily between us

Best regards


author: Gezim Shehu [Communardo]
body: Hi,

Personally, I tend to move far from the folder concept. I've seen better organization by using labels/tags.

Folders usually have a tree structure, so the analogy would be 1 to 1 to Confluence pages.

1 Page is 1 folder (even if it has contents or not).

So in theory you could use "empty" spaces as folders or containers.

Regarding space to space communication, I believe there are some add-ons which can help, but generally excerpt include and excerpt macro cover the basic stuff.

<https://confluence.atlassian.com/doc/excerpt-macro-148062.html>

I hope I answered your question.