The privileges a user has within Tasxs depend on the roles he has been assigned to. It is a two-tier mechanism:

• Users are assigned to roles
• In a job, you can specify a role for each of the following permissions:
  • View: Users in this role are allowed to see the job and the execution history and results.
  • Edit: Users in this role are allowed to edit the job.
  • Execute: Users in this role are allowed to start the job.

System Roles

Tasxs comes with the following system roles, which grant it's members certain application-level privileges.

• User: any user of Tasxs must be part of this role.
• Manager
• Administrator: Grants administrator privileges to it's members, allowing them to administer every aspect of Tasxs.

These roles can be used to grant access to jobs just like any other role, but they can't be deleted.

Permission Inheritance

It is important to be aware of the fact that roles defined in jobs are inherited just like parameter values. To easily manage access to Tasxs jobs, you should work out a inheritance structure for your jobs that matches your security needs.