Departments And Hierarchy | teamgram

Departments And Hierarchy

Administrators may define an organizational chart for your company and determine which users are in each department.

The organizational chart has some important security implications.

Granting Rights by Departments Instead of Individuals:

While it is possible to grant reader- or editor-level access to each record both by user and by department, authorizing departments instead of individual users has some important benefits:

Instead of granting John editor access to a deal, I can create a department called Sales Manager, make John its only member, and then grant access to the Sales Manager department.

That way, if John leaves this position and a new Sales Manager is appointed, I can automatically grant her access to all previously saved documents simply by making her a member of the Sales Manager department.

Upward Propagation of Access Rights:

Simply put, this feature means a manager automatically has all of the collective rights of everyone reporting to him or her.

Imagine the following case:

  • Sales Manager department has John as its only member. Sales Manager department reports to another department called CEO.
  • Sales Reps department contains 3 users: Mike, Jennifer, and Paul. This department reports to the Sales Manager department.

Mike shares a note, and only grants reader access to Jennifer. That means Paul cannot read this note.

However John and the CEO can still read this note, because they are higher up in the hierarchy.

This feature ensures that no data can be made inaccessible to everyone in TeamGram. It also makes granting rights a lot simpler.