AgileApps Support Wiki Pre Release

Difference between revisions of "Roles"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 1: Line 1:
'''Settings > Administration > Roles'''
'''Settings > Administration > Roles'''


Roles are categories of users. Permissions can be assigned to a role. Then, as individual users move into and out of those roles, they acquire or drop the associated permissions.
==About Roles==
Your organization will be more effective when your users can get the information they need, when they need it. Sales representatives use data differently than marketing managers, VPs, CEOs or the folks in accounting. For example, a sales rep making cold calls needs a telesales application with activity logging capability, while a senior manager presenting to staffers may need structured, summary reports to manage overall business goals.
Your organization will be more effective when your users can get the information they need, when they need it. Sales representatives use data differently than marketing managers, VPs, CEOs or the folks in accounting. For example, a sales rep making cold calls needs a telesales application with activity logging capability, while a senior manager presenting to staffers may need structured, summary reports to manage overall business goals.


Line 13: Line 16:
*[[#Role Based Access Permissions|Role Based Access Permissions]]
*[[#Role Based Access Permissions|Role Based Access Permissions]]


 
===Guidelines===
==Guidelines==
{{:User, Team and Role Guidelines}}
{{:User, Team and Role Guidelines}}


==Considerations==
===Considerations===
Each role can include a combination of any of the following permissions:
Each role can include a combination of any of the following permissions:
*Update, Delete or View records owned by other Team members  
*Update, Delete or View records owned by other Team members  
Line 26: Line 28:
==Role Based Access Permissions==
==Role Based Access Permissions==
{{:Role Based Access Permissions}}
{{:Role Based Access Permissions}}
<noinclude>


<noinclude>[[Category:Administration| 3]]</noinclude>
[[Category:Administration| 3]]
<noinclude>[[Category:Glossary]]</noinclude>
[[Category:Glossary]]
</noinclude>

Revision as of 18:16, 29 July 2011

Settings > Administration > Roles

Roles are categories of users. Permissions can be assigned to a role. Then, as individual users move into and out of those roles, they acquire or drop the associated permissions.

About Roles

Your organization will be more effective when your users can get the information they need, when they need it. Sales representatives use data differently than marketing managers, VPs, CEOs or the folks in accounting. For example, a sales rep making cold calls needs a telesales application with activity logging capability, while a senior manager presenting to staffers may need structured, summary reports to manage overall business goals.

In an organization, employees have authority over information in different areas - they play different roles in each situation. In the platform, parallel roles can be defined to automatically manage access to that data. The information each employee needs to perform a task becomes available, and can be shared with a team of employees.

When role based access permissions are defined, users get streamlined views and reports, access to process-based workflow and the ability to complete their work online, in one place, with no extraneous information to distract from their flow. Roles are intended to control access, but they also add needed structure.

Learn more:

Guidelines

In conjunction with Access Profiles, the combination of Team and Role assignments controls the user's ability to view and access data.

  • Users
  • Users can be members of multiple Teams
  • When users are given access to an application, they are assigned one or more Roles
  • Roles
  • Roles are defined for applications
  • Roles define the types of data users can access and share with other team members
  • Default Roles are available in the platform
  • Additional roles can be created and the default roles can be modified as needed
  • Teams
  • Each user must be assigned to a Primary Team.

Considerations

Each role can include a combination of any of the following permissions:

  • Update, Delete or View records owned by other Team members
  • Create or Delete records for each Object in the platform
  • Grant or deny User access to web tabs
  • Administer the platform

Role Based Access Permissions

Role Based Access Permissions