Jibility Enterprise Plan supports the ability for customers to have a separate customer environment that enables single sign-on and self-management of team members.

With single sign-on enabled, the customer's users are automatically authenticated for access to Jibility, and no registration process is required. However, access permission is still needed to use Jibility, and a license is also required for editor users. Jibility user permission is managed by the customer's Jibility administrator using the "Manage Team" function.

The Jibility Enterprise Team Management function supports the ability to

1) Add users and assigned them a Viewer, Editor or Admin role

2) Remove team members and enable the Admin to reassign the removed users' roadmaps to a new owner.

To open the Manage Team function, select "Manage Team" in the drop-down menu from the Account icon, as shown below. You will find the account icon in the top right corner of your Jibility home page.

Note, that only the customer's Jibility administrator can access the Manage Team function.

On set-up of the customer environment, a nominated customer's Jibility administrator is configured by Jibility support. The customer Jibility administrator is the first Jibility user, and this person can use the Manage Team function to add other team members, as required.

In the following example, Mayur Preece is the customer's Jibility administrator, and she is about to add Wesley Kennedy as the second user.

To access Jibility, each user must be a member of the customer's team. A user is added by the customer's Jibility administrator, and each user added can have one of the following roles.

To add a user, the administrator must enter the new user's name, email address, and role in the "Invite User" section and click the Add button. The user is added into the Team Members list, but you must also click the "Apply" button to save this change.

In the following example, a new user, "Addison Reid", is about to be added.

IMPORTANT: Jibility does not validate the users added to your team against your identity provider. That is, you can add users and an invitation email is sent to the user, but if that user is not a valid user or does not have permissions to access Jibility, as controlled by your identity provider, then they will not be able to accept the invite, so the team membership process is not completed.

After adding a new user, the license count is updated, as shown below. In this example, only the Editor and Admin are licensed users.

After adding a user to a team, the new user will receive an invitation by email. The invited user must click on the accept button to complete the process. An example of the invitation to join email is illustrated below.

NOTE, the user accepting the invite must have permission to access Jibility through the customer's identity provider.

Against each team member is their status, as shown in the example below.

The team member status can be one of the following values.

A team administrator can delete or remove a team member by selecting the "Remove" button for the corresponding team member. To save the removed user changes, select the "Apply" button. You can remove multiple users and apply all the changes as a batch.

Note, the roadmaps belonging to a removed team member are automatically moved to the Administrator's (person who applied the delete) home page for re-assignment. Please refer to Assigning Removed Team Member's Roadmaps.

Tips, after selecting remove and before applying, you still have the option to Undo the removal. Once you have applied the change, then the user is permanently removed.

If you are a team administrator, then you can remove team members. After removing a team member, their roadmaps are automatically delegated to you for re-assignment. i.e. You can re-assigned a removed user's roadmaps to an alternate owner.

Note, the removed user's roadmaps are delegated to you for re-assignment but to maintain roadmap document confidentiality you cannot open the roadmaps.

In the following example, Mary Jane and John Smith were removed from the team. Mary's "Acme Strategic Roadmap" and John's "IT Strategic Roadmap" are shown on the admin user's home page under a special "To be assigned from xyz" section.

You can choose to

1) Delete the roadmaps previously owned by a removed team member; or

To delete the roadmap, select the three vertical ellipses, and the Delete menu will display (as shown below).

2) Assign the roadmaps to a new owner.

If you are an administrator and remove a user from your team, their roadmaps will be in your home page under a "To be assigned from xyz" section.

When you choose to re-assign a removed user's roadmaps, the people you can assign the roadmap to will depend on whether the roadmap was previously shared with other users:

1) A removed user's roadmap shared with other users

You can assign a new owner from the list of the shared users. i.e. You cannot assign the roadmap to a user who was not previously privy to the content of that roadmap.

2) A removed user's roadmap not shared with other users

You can assign a new owner from the team's list of all Editor users. Given that the roadmap was not previously shared, you must decide who is the best alternate owner of the roadmap based on the list of available editors.