Configuring Security in RiteTrack3

Webinar, March 28th, 2008

Jim Drever, Marketing DirectorJustin Olson, Deployment Manager

Our Agenda

• What is the Admin Tree (useful if you are new to RiteTrack 3)

• Go Through the tree’s nodes• Discuss how basic security works• Make an event’s details invisible to a group• Conclude with questions and topic ideas for

the next webinar

The Tree

• You have to have Administrative rights• There is no extra password protection• Lets go see

Four Node Types

• Users – Manage individual users• Security Groups – set group policies• Organization Configuration• Lock Types

Users node

• Each User (someone with a log in into RT)– Selecting a user lets you edit their account

(passwords, anyone?)

• SubNodes of Each User– Groups – Which Group are they part of?• Assign a user to a group. Instead of setting up each

person, set up the security for the group

– Tree Views – What trees does a user get to see (note the admin tree?)

Security Groups

• This is where we set up most of the security• Select the Group (right click will make a new

one) and let look at that form– Name– Description– Priority – When a user has several, which should

have priority… Administrator is usually 1– Active– Group Users (from assigning users in user node)

A Quick Look

View Permissions (Under Group)

• Give basic read, write, create and delete permissions to specific presentation objects

• Use “Global” to give or deny permission to all objects of a specific type (e.g., all forms)

• Use global first, the assign specifics if needed

Entity Permissions

• Add permissions to entities for specific security group

• Use for relational security • For example, a group can only see clients they

manage and no others

• Please let Handel set this up for now, as it does require some database set up

Function Permissions• Add/Delete Function permissions

- for example drag and drop functionality

Policies

• Add policies to a specific group• Set a property for a specific control (e.g.,

disable SSN for a specific group)• Handel staff configure policies before setting

in administrator

Tree Views

• Add or remove default tree views• Inherit tree views when adding a user to a

security group

Lock Type Override

• When Events are closed and other items are locked, these enable them to be unlocked for groups

• Disable closed and signed events• Give administrators access to specific forms

on signed or locked events• If no row exists for a specific lock type, then

the object will be LOCKED for the security group.

Lock Types (Organizations in a Sec)

• The last part we looked at in setting up security for lock type overrides gets the lock types from here

• Developed with configuration to show here

Organizations

• Regular settings, Lets take a quick look…

Basic Hierarchy

• There are multiple groups at an organization• Administrator Group (always)• User Groups• Sometimes (many) more• A user can be part of more than one group• Security is based on the priority of that group

(remember the Security Group form?)

Lets Pretend…

• We are an Indian tibe• We have enrollment• Supervisors maybe some should or shouldn’t

have access to details• In this case, lets look at• The name of this event in this database is

“enrollment”

Let Us Set This Security Up

• Several groups CAN be exactly the same EXCEPT the Intake should have limited access to the enrollment event.

• Let us change this in our current system:

Finally, Future Webinar Topics?

• Let’s hear them• Or, e-mail Jim@HandelIT.com

• Next Webinar Date: July 8th, 2008 – (I will e-mail you beforehand)

Thanks!