User-level security: Roles and Groups

Together, security roles and security groups let you control access to the ASP.NET-based features of iMIS; in contrast, older features of iMIS are secured using authorization levels (see Authorization levels: Desktop views). Security role and group assignments are defined in user records.

• Security roles grant specific administrative privileges to user records. For example, one security role might let you use and edit an iMIS definition object in the Document System, while another role might let you use that object but not edit (or even see) its properties.
• Security groups control which iMIS features group members see and which capabilities within each feature they can use.

📘

Note

User-level security is separate from object-level security (see Preconfigured security sets), which restricts objects (folders, queries, reports) in the Document System.

Roles: SysAdmin

The default SysAdmin role grants privileges much like those of the MANAGER user record. Only a Full user can be a SysAdmin. Each SysAdmin can:

• Edit user records, including logon names (unless that privilege is disabled in the web.config file for iMIS)
• Use System Setup
• Use Tools (if licensed)
• Administer Issues (if licensed)
  • Start e-mail server
  • Set up module

Groups

The following table describes the security groups that affect user privileges.

Group membership controls web access

Group membership determines whether a user sees Marketing and/or Process Manager from a web client.

• To grant access to Marketing, place users in one of these groups:

  • CampaignAdmin
  • CampaignMgr
  • CampaignUser
  • RFMAdmin
  • RFMMgr
  • RFMUser
  • SegAdmin
  • SegMgr
  • SegUser

• To grant access to Process Manager, place users in one of these groups:

  • OpportunityAdmin
  • OpportunityCreator
  • OpportunityMgr
  • OpportunityOwners
  • OpportunityUser

📘

Note

Casual licensing prevents access Marketing or Process Manager, regardless of group assignments.