1.6		Using Windows Authentication	install admin
8		People and Permissions	admin
8.1		Users	admin
8.2		Groups	admin
8.3		Permissions	admin
8.4		Active Directory Integration and Windows Authentication	admin
10.10.2		Users & Security	admin
10.10.2.1		User Management	admin
10.10.2.2		Global and Project Groups	admin
10.10.2.3		Working with Global Groups	admin
10.10.2.4		Working with Project Groups	admin
10.10.2.5		Available Permissions	admin
10.10.2.6		Project Resources	admin
10.10.2.7		Assigning Permissions to Projects	admin
10.10.2.8		Windows Authentication	admin
10.10.2.9		Active Directory Integration	admin
10.12.10		Groups API	api
10.12.13		Users API	api

18 documents found.

Navigate to the Customization section from the Customize link in the top right hand section of the menu. If you are a Gemini Administrator you will then be able to navigate to the People tab and the Permissions sub tab (see below).

To Add a new User Permissions set, click on the Add button. You will be prompted to provide:

• Permission Set Name
• Description

Click Save to create the Permission Set.

To maintain the description of the Set, click in the field and use Gemini’s inline editing to easily and instantly change the field value. To delete a Permission Set click on the Delete icon to the right of the screen. If the Set contains members you will be warned that its deletion will result in changes to the permissions of those users and allowed to proceed or abort the operation.

Assigning Permissions to Projects and Users

Once the Permission Set has been created you will need to specify two things:

1. The projects to which the permissions apply
2. The Groups that are to be granted the permissions in this Set

To do this, click on the Edit icon. You will see the following screen:

Click in the “Associated Projects” field to get a list of Projects in the system. You can select as many projects as you like to relate to a Permission Set.

Granting permissions on projects to Groups is a simple process of selecting the Groups containing users who have the permission on the specified project(s) in a point-click-select method, against each permission. If a permission is not granted to any Group then by default the action cannot be performed on the projects specified in the “Associated Projects” field. Only those Groups selected to have the specified permission will be able to action it.

Gemini has the following Permissions:

* Please note that in Gemini terminology an ‘item’ represents any type of task. An ‘item’ could therefore be a case, a bug/issue, a story, an inquiry, a document workflow etc. The most generic way to regard an ‘item’ in Gemini is to think of it as a task to be tracked and managed.