Organizations in RIDE Server

Organization allow to regroup developers on RIDE Server and allocate resources. Resources and permissions are controlled and allocated within RIDE Server admin dashboard by system administrator.

Roles

There are two main different roles in an organization:  

  • Admin: Organization's admins are able to manage the organization. Admins can edit settings, manage members, resources and sub-organization.  
  • Members: Organization's members are able create workspace, manage own workspaces and use any other workspaces they have permissions for.  

Alternatively there is System Admin role, on RIDE Server System, who is able to create root organizations, manage all the resources, members and sub-organizations.

Organization Workspaces

Workspaces created in an organization use organization resources granted and allocated by the system administrator.

Organization Workspace Resources

Resources for organization are taken from the parent one. Admins can control whether all, or a portion of the resources, that are shared with the sub-organization.  

Organization Structure

Organizations can have sub-organizations.
Root organizations are the starting point of each group of developers. Multiple root organizations are allowed onto your system. Root organizations can be created only be the System Admin. The management of the root organization's resources is also allowed only to the System Admin of your RIDE Server installation.

Creating an Organization

RIDE Server system administrator is able to create organizations.   

To create an organization, use the menu in the left sidebar, which leads to the list of organizations:  

A new page is displayed with all organizations in your system. Click on the top-left button to create a new organization.

A new page is displayed in which an organization name should set and organization members may be added.

Organization List

The list of all organizations are displayed on organizations page:

The list contains the general information for each organization: number of members, total and available RAM and number of sub-organizations.

Adding Organization Members

Adding organization members by clicking the "Add" button will display a new popup. You can add multiple users at the same time by separating emails with a comma but note that all users added at the same time will be given the same role:

You can change an organization member's role or remove them from the organization at any time.

Note: Users with the green checkmark beside their name already have an account on your RIDE Server system and will be added to the organization. Users without a checkmark do not have an account and will not be added into the organization.

Workspaces in Organization

Workspace is created inside of an organization and uses the resources of this very organization. Workspace creator has to choose the organization on workspace creation page:

Create Sub-Organization

The creation of sub-organization can be done from organization details page by selecting Sub-Organizations tab and clicking "Add Sub-Organization" button.
The flow of sub-organization creation is the same as for orhanizations.

Add members to Sub-Organization

The sub-organization members can be added only from the list of parent organization's members:

Organization and Sub-Organization Administration

Organization settings are visible to all members of the organization, but only the RIDE Server system administrator is able to modify the settings.

Rename an Organization or Sub-Organization

Action restricted to: RIDE Server system administrator and admins of the organization.

To rename an Organization, click in the "Name" textfield and start editing the name of the organization. Once edited, the save mode will appear - click on "Save" button to update the name.

The name of the organization is restricted to the following rules:  

  • Only alphanumeric characters or a single "-" can be used  
  • Spaces cannot be used in organization names  
  • Each organization name must be unique within the RIDE Server install
  • Each sub-organization name must be unique within an organization

Leave an Organization or Sub-Organization

This action is not possible for members of an organization. Users have to contact organization's admin or RIDE Server system admin.

Delete an Organization or Sub-Organization

Action restricted to: RIDE Server system administrator and admins of the organization.

To delete an organization or a sub-organization, click on "Delete" button.
This action can't be reverted and all workspaces created under the organization will be deleted.

All members of the organization will receive an email notification to inform about organization deletion.

Manage Organization and Sub-Organization Limits

Action restricted to: RIDE Server system administrator and admins of the organization.
The organization default caps are taken from the system configuration. The admin of the organization can manage only the limits of it's sub-organizations.
By default, there are no resource limits applied to the organization so all members can benefit from all the allocated resources. If an organization admin wishes to set limits they have three options:  

Update Organization and Sub-Organization Member Roles

Action restricted to: RIDE Server system administrator and admins of the organization.

To edit the role of a organization member click on the "Edit" button in the "Actions" column:

You'll get a popup where you can update the role of the selected member:

Click "Save" to confirm the update.

Remove Organization and Sub-Organization Members

Action restricted to: RIDE Server system administrator and admins of the organization.

To remove a member from the organization, you can click on the "Delete" button in the "Actions" column:

You'll get a confirmation popup, where you can confirm or cancel your action.

You can also select multiple members from the organization, using the checkboxes. A delete button will appear in the header of the table:

The members that are removed from the organization will receive an email notification.

Did this answer your question?