cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
545
Views
2
Helpful
1
Replies
Highlighted
Beginner

Teams and Rooms - how to better understand design, configuration, security?

Hello, we are considering adopting Cisco Spark internally, and are running a bit of a pilot with the free version.

It seems the architecture is:

Create Team 1

   - default "General" room is created

   - Create Room A (invite members of Team 1, and guests)

   - Create Room B (invite member of Team 1, and guests)

    .

    .

As I understand it, any "Team 1" member could join, leave, rejoin any Room under "Team 1" at any time.  Is this correct?

But once you leave a team (the last room you are a member of within the team), you no longer have any visibility into the Team's existence. It this the correct understanding?

If we adopt the paid version could members of our company look across "open teams" and join them much like rooms?  Is there some deeper design guide and philosophical direction whitepaper as to the organizational/security architecture of teams and rooms?

I'm finding I would like to be able to create many adhoc teams within our larger IT staff, and if permissions would would determine allow, enable the larger IT staff to browse and view the activity in the teams and rooms underneath, but there doesn't seem to be a way to do this today.

Anyone else encounter this or have advice on how other solutions handle this?

1 REPLY 1
Highlighted
Cisco Employee

Hello, we are considering adopting Cisco Spark internally, and are running a bit of a pilot with the free version.

It seems the architecture is:

Create Team 1

   - default "General" room is created

   - Create Room A (invite members of Team 1, and guests)

   - Create Room B (invite member of Team 1, and guests)

    .

    .

As I understand it, any "Team 1" member could join, leave, rejoin any Room under "Team 1" at any time.  Is this correct?

          Yes

But once you leave a team (the last room you are a member of within the team), you no longer have any visibility into the Team's existence. It this the correct understanding?

          Correct

If we adopt the paid version could members of our company look across "open teams" and join them much like rooms?  Is there some deeper design guide and philosophical direction whitepaper as to the organizational/security architecture of teams and rooms?

          Teams are just that a team of folks you work with that you do not want to open publicly.

          There are a couple documents/video:    

               Cisco Spark: Create and Manage Teams (Browser/Desktop) - YouTube

               Cisco Spark Team Details | Cisco Cloud Collaboration Help Central

I'm finding I would like to be able to create many adhoc teams within our larger IT staff, and if permissions would would determine allow, enable the larger IT staff to browse and view the activity in the teams and rooms underneath, but there doesn't seem to be a way to do this today.

          You could create a larger IT team and create the adhoc rooms under that team which then are discoverable.

          There is no team within a team aspect

Anyone else encounter this or have advice on how other solutions handle this?

Content for Community-Ad