System Administration

Delivered Security Definitions

Security definitions are provided for delivered WebApps. The Stewardship Tier is delivered with security definitions that have events and keys for delivered components. Delivered security definitions have the SYSTEM PROVIDED check box checked, and cannot be updated.

The following security definition for delivered WebApps are included in the Stewardship Tier. The key column assigned to the security definition restricts access to that object. The event rules registered to the security definition list rules that run when events assigned to the security definition occur.

These security definitions should be used to define the security of users for the delivered components of the Stewardship Tier.  Custom WebApps need custom security definitions created in order to provide data level security to those applications.

Security Definition Name

Key Column Assigned

Event Rules registered

Console.Source 

Source in ADM

No rules assigned

Console. Wave_ProcessArea

Wave Process Area in ADM

No rules assigned

Console. Wave_ProcessArea_Object

Wave Process Area Object in ADM

No rules assigned

DGE.Position

Position in MDM
  • When a User is deleted, delete the User from ttPositionUser.
  • When a User is added to a Security Role, add User to ttPositionUser if the User is not already there.
  • When a User is removed from a Security Role, delete User from ttPositionUser if the User does not have permissions through other roles.
  • When a Key is added to a Security Role, for Users that have the Key, add User to ttPositionUser if the User is not already there.
  • When a Security Role is deleted, delete User that has that Security Role from ttPositionUser if the User does not have permissions through other roles.
  • When a Security Role is deleted, delete User that has that Security Role from ttPositionUser if the User does not have permissions through other role.
  • Add User to ttPositionUser for newly added Key if the User is not already there.
  • Remove User from ttPositionUser whose Key is deleted
  • When a User is removed from a Security Role, delete User from ttPositionUser if the User does not have permissions through other roles.
  • When a User is added to a Security Role, add User to ttPositionUser if the User is not already there.
  • When a User is removed from a Security Role, delete User from ttPositionUser if the User does not have permissions through other roles.
  • When a User is added to a Security Role, add User to ttPositionUser if the User is not already there.

DSPCommon.Administrator_Role

Provides access to everything in Collect and ADM

No rules assigned

DSPCommon.Analyze.DataSourceID

Data Source in Common and Collect

No rules assigned

DSPCommon.Collect.Targets

Targets in Collect

No rules assigned

DSPCommon.Integrate.Categories

Categories in Integrate

No rules assigned

DSPCompose.Team_Template_Role

Template roles in Mass Maintenance
  • When a User is deleted, delete the User's access to Template Role and delete the user from ttUser.
  • Add User to Template Role when user is added to Security Role
  • When a User is removed from Security Role, Deny access to Template Role
  • When a Key is added to a Security Role, for Users that have the Key, add User to the Template Role.
  • When a Key is removed from a Security Role, remove access to User to the Template Role of the user does not have permissions through other roles.
  • When a Security Role is deleted, Remove Users access to access to Template Role from that Security Role, if the user does not have access from other Roles.
  • Grant Users access to newly added Key if the User is not already there.
  • When a Key is removed from a Security Role, remove access to User to the Template Role of the user does not have permissions through other roles.
  • When a User is removed from a Security Role, remove access to Template Role if the User does not have permissions through other roles
  • When a User is added to a Security Role, add User to ttUser if the User is not already there and update the Template Role access.
  • When a User is removed from a Security Role on the User Role Staging page, remove access to Template Role if the User does not have permissions through other role
  • When a User is added to a Security Role on the User Role Staging page, add User to ttUser if the User is not already there and update the Template Role access

dspMonitor.Group

Groups in Data Quality
  • When a User is deleted, delete the User from ddGroupUser.
  • When a User is added to a Security Role, add User to ddGroupUser if the User is not already there.
  • When a User is removed from a Security Role, delete User from ddGroupUser if the User does not have permissions through other roles.
  • When a Key is added to a Security Role, for Users that have the Key, add User to ddGroupUser if the User is not already there.
  • When a Key is removed from a Security Role, delete User that has that Security Key from ddGroupUser if the User does not have permissions through other roles.
  • When a Security Role is deleted, delete User that has that Security Role from ddGroupUser if the User does not have permissions through other roles.
  • Add User to ddGroupUser for newly added Key if the User is not already there.
  • Remove User from ddGroupUser whose Key is deleted.
  • When a User is removed from a Security Role, delete User from ddGroupUser if the User does not have permissions through other roles.
  • When a User is added to a Security Role, add User to ddGroupUser if the User is not already there.
  • When a User is removed from a Security Role on the User Role Staging page, delete User from ddGroupUser if the User does not have permissions through other roles.
  • When a User is added to a Security Role on the User Role Staging page, add User to ddGroupUser if the User is not already there.

DSPTrack.Plan.ProjectID

Project in dspTrack
  • When a Key is added to a Security Role, for Users that have the Key, assign default calendar as defined in Track Parameters.
  • When a User is added to a Security Role, Assign the user the Default calendar mentioned in Track Parameters.
  • When a User is added to a Security Role, assign default calendar defined at Track Parameters to the User
  • Assign User to default Calendar when the User Specific Security Definition is added
  • When a user is deleted, remove record from DSPCommon..ttUserCalendar if it exists

DSPTrack.Project.ProjectCollectionID

Plan in dspTrack
  • When a user is deleted, remove record from DSPCommon..ttUserCalendar if it exists
  • When a User is added to a Security Role, Assign him the Default calendar mentioned in Track Parameters.
  • When a Key is added to a Security Role, for Users that have the Key, assign default calendar as defined in Track Parameters.
  • Assign User to default Calendar when the User Specific Security Definition is added
  • Assign User to default Calendar when the User Specific Security Definition is added
  • When a User is added to a Security Role, assign default calendar defined at Track Parameters to the User

DSPTrack.WorkListSetup.WorkListID

Work List item in dspTrack

No rules assigned