AgileApps Support Wiki Pre Release

Difference between revisions of "Roles"

From AgileApps Support Wiki
imported>Aeric
m (Text replace - 'Settings > Administration > Roles' to 'Designer > Roles')
imported>Aeric
Line 11: Line 11:


;Roles, Users, and Teams:
;Roles, Users, and Teams:
:* Each [[User]] in a [[Team]] is assigned a Role.
:* Each [[User]] in an application is assigned one or more Roles.
:* Users can have different roles in different teams.
:* Users select which Role is active, at any given time.
:* Users can also have different roles in the same team. In that case, they have the combination of permissions defined by those roles.
:* Users can have different active roles in different browser windows.


;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:
:*Create or Delete records for each Object in the application
:*Update, Delete or View records owned by other Team members  
:*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


''Learn More:'' [[Default Roles]]
''Learn More:'' [[Default Roles]]

Revision as of 22:20, 20 June 2012

Designer > 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.

Roles, Users, and Teams
  • Each User in an application is assigned one or more Roles.
  • Users select which Role is active, at any given time.
  • Users can have different active roles in different browser windows.
Considerations

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

  • Create or Delete records for each Object in the application
  • Update, Delete or View records owned by other Team members

Learn More: Default Roles

About Role Based Access Permissions

Role Based Access Permissions