Permissions and Relationships

Permissions

Permission Groups in the DrawBridge Console are analagous to User Groups in typical operating systems.

Permissions Groups are a way of assigning a particular Role to a Person: Adding a Person record to the Accountabilty permission group gives them the access and controls exclusive to Accountability and higher level permission groups.

Person records are given the permissions by being added as a member of a particular Permissions Group.

Permission Groups in the DrawBridge Console are as follows:Console:

(requireswith
• Appstore
Access
anassociation

Permission Group	Required Relationship	About
Company Owner	Company associationOwner	The owner of a Company
Appstore Access	Company or Accountability Policy	Allows Person to Enable App Store Access on a Company record)record
Can Submit Autofix Requests	Company	Allows use of the Autofix reclassification function
Can Submit Sites for Human Review	Company	Allows submission of a Classification Review support ticket
Media Viewer	Company	Allows classification of a video in the Media Room
Company Media Room Admin	Company	Allows administration of a company Media Room
Report Viewer	Company or Accountability Policy	Allows viewing of web activity Reports
System Owner	Company Owner	Allows visibility and control of all Tenant Companies on that DrawBridge
ACL Pumpkineer	Accountability Policy or Compass Foundation Staff	Allows creation and modification of ACLs
Accountablity	Accountability Policy	Allows visibility and control of member Company configurations and reports
Device Detector Admin	(requires?)	(?)
Realtime Log Viewer	Company Owner of Main Company	Allows access to the Mainsystem-wide Company record) ACL Pumpkineer Accountablity (requires an Acountability Policy Contact association) Device Detector Admin Realtime Log Viewer
Reseller	(?)	Allows visibility and control of all Tenant Companies on that DrawBridge
Sysadmin	(?)	(?)

Relationships

Records in the DrawBridge console, particularly Person records, can have one or more relationship associations.

For an analogy, consider how individual people in real life have different relationships to others, depending on their role: Parent-Parent, Parent-Child, Brother-Sister, and so forth.

Relationships in the Console

are as follows:

A Person can have the following relationships to Companies:

• Owner
• Associate
• Tech Support
• General Contact

A Person can have the following relationships to an Acountability PoliciesPolicy:

• Accountability Contact

Company A Company can have the following relationship to an Accountability Policy:Policy:

• Member

---

Migrated from Accounts; needs cleaned up to just analogy detailExamples

People,Person Companies,fred_smith owns Company Eastwood Trading Co. He therefore is assigned a Company Owner Relationship, and Accountability Policies:

The three types of records all play together: the flexible design of the DrawBridge Console accomodates the association of a single Person record to multiple entities (Companies/Accountability Policies). This can be leveraged to enable one Person to have accessadded to the settingsCompany Owner Permissions Group.

Company Eastwood Trading Co. has an on-premises DrawBridge, so fred_smith is also added to the System Owner Permissions Group.

Person jack_miller is on the IT staff for Eastwood Trading Co. He is assigned a Tech Support Relationship, and reportsadded of multiple companies.

Person

For example, Person david_martin can be a Company Associate of Fred's Construction, as well as an Accountability Contact into the GoldenSysadmin SandsPermissions Christian Fellowship Accountability Policy, which will give him access to all member companies of the Golden Sands Christian Fellowship accountability policy.Group.

The Permission Groups assigned to a Person record control the access and capabilities of that Person in the DrawBridge Console. A Person can have the following Permission Group membership:

Also, a person can be a member of the following Permission Groups for more specialized functions: