3 Replies Latest reply on Oct 11, 2016 11:14 AM by jesse.fuller

    Adding non space users to project

    jonathanhansen

      A lot of our projects are cross team but it seems if we place a project in a team space we cannot adjust who is involved or invite others.

      Do we have to create a new space just to get people outside our team into a project? Seems poorly thought out for collaboration.

        • Re: Adding non space users to project

          Hi Jonathan,

           

          Reviewing through your description, this will depend on your specific instance's place structure and permission's configuration. For reference, if a project is located within a specific place it will inherit permissions from that place, so it's possible you have placed these projects within restricted places in your instance and are seeing the expected beahvior.

           

          As such, by adding these additional users to the place where the project is located should provide them with access.

           

          Thanks!

            • Re: Adding non space users to project
              jonathanhansen

              So you need to make a group and then a project under the group just to work with people not on your team on something? Very strange and not intuitive nor collaborative at all. Projects should have their own access permissions.

               

              This makes spaces more or less useless for us, everything will have to be groups. Our company is not very siloed nor should our collaboration software encourage that behavior

                • Re: Adding non space users to project

                  Hi jonathanhansen

                   

                  So you need to make a group and then a project under the group just to work with people not on your team on something?

                  This will depend on your specific instance's structure. However, projects will utilize any permissions you have configured for the parent place, so is something to consider when planning out the structure of your instance.

                   

                  This makes spaces more or less useless for us, everything will have to be groups. Our company is not very siloed nor should our collaboration software encourage that behavior

                  As you mention your company is not very siloed this will most likely work out well as open access groups and non-restrictive spaces should allow your users to access projects contained within those places.

                   

                  Lastly, you might find the following improvement idea Bring permissions to jive projects interesting as it purposes a separate permission structure for projects. If so, please help to vote it up so that it raises awareness with our Product team.

                   

                  Thanks!

                  1 person found this helpful