From Net-Results Support
Roles allow you to control which users have access to which "objects" in Net-Results. (Profiles are separate, in that allow you to control which areas of the system may be accessed by a given user.)
Think of roles in terms of ownership. For example, you can create an item and either assign it to your own role (owned by you) or the global role (owned by everyone).
Roles in Net-Results take the form of a hierarchy. A member of a given Role has the ability to view/change objects controlled by any subordinate or "child" Roles "beneath" their Role in the hierarchy as well as any objects controlled by their Role.
- A default Role exists in your Net-Results account and is named after your company.
- You do not have to create any additional Roles if you do not choose to. You can safely ignore the existence of Roles if you like.
You may create a Role called U.S. Sales. You may create "child" Roles called East Coast Sales and West Coast Sales.
Users assigned to the U.S. Sales Role will have view/change permissions on all objects created by users in any of the three Roles in this example.
Users in the East Coast Sales and West Coast Sales Roles will have no permissions to objects "owned" by the U.S. Sales Role.
Objects to which you have no permissions will not appear in the interface. In the example above, a List created by a user assigned to the U.S. Sales Role will not even be visible to a user assigned to the West Coast Sales Role.
Objects over which Roles exert control include:
- Web Form Mappings