Setting Up and Managing Security September 18, 2013 Valerie Balaski & Tamara Wojdylo

1. Setting Up and Managing SecuritySeptember 18, 2013Valerie Balaski & Tamara Wojdylo

2. Beginner Track – AM session • Security settings define the level of access your users have to all areas of The Raiser’s Edge. • A first level of security determine what the user can SEE = view. • A second level of security settings determine which fields can be changed, and whether the user canadd, edit, or delete records – when drop down menu has items greyed out, the user does not have that permission. The user can perform various functions throughout the program. • Security centers around the groups you create. • You can customize the security settings for a group and then add members to the group based on the level of access granted. • Security is closely linked with Configuration to determine how The Raiser’s Edge manages information. Configuration tab is ONLY available to users with Supervisor rights.

3. Accessing Security • Admin • Security

4. Setting Up a New User • We recommend you first set up the NEW user as an individual constituent, then make them solicitorbecause ONLY solicitors can be users. • Changing passwords • User options • Windowsauthentication,not recommended

6. Password options • Best practice: set up new users before they start at the organization, offering the credentials to their manager. Recommending a one to one RE introduction session, which includes how to “change password” to something private from the Edit menu. • In Configuration, you can set a business rule to allow passwords to expire after a specific number of days. If you enable password expiration, all users automatically receive rights to change their passwords.

7. Copy from (button)…

8. Plug in available: Copy user settings from one user to another

9. Managing Security

10. Administration - Security • The first step to establish security for The Raiser’s Edge is to create security groups. • Give the groups descriptive names you can easily identify. Does it make sense for each operational OR functional area to have same rights? • Assign privileges to groups based on the areas of the program to which you want its members to have access. For example, a group that contains experienced users may have access to Administration functions such as Import and Globally Delete Records. OR should deleting rights be limited to one or two people?

11. Creating, editing and deleting Security Groups

12. Security Options • If you add the Supervisor as a member of a security group, Supervisor rights are not affected. • If a user belongs to multiple groups, the rights in the groups are combined. However, this does not apply to system level security (Gift Security by Fund, Notepad Security by Type, and Constituent Security by Constituency). If a user belongs to one group that has system level rights to records and another that does not, the user does not have rights to those records. We recommend you do not assign users to multiple security groups.

13. Add or Remove users from a Security group • When you remove a user from a Security group, you are not deleting them as a user nor as a constituent in the database. • Note: A user cannot delete its own security record

14. When to delete a user from accessing RE? • If staffing changes are known in advance then removing the user at the end of their last day is best. • When an employee leaves unexpectedly, delete ASAP. • Another method of deleting a user is toright click on theirname under users in the Security window.

15. Q & AValerie.Balaski@vancouver.catamara.wojdylo@vghfoundation.caThanks for joining us!