# Organization, Account and Team Settings
One of the key inefficiencies throughout the Machine Learning field is collaboration (or lack there of). With large datasets, complicated file structures, hundreds of different models and various different projects, managing an team can be the hardest part of a successful data science workflow.
Addressing this issue is at the heart of cnvrg. The cnvrg platform has comprehensive organization and team management features which allows you to streamline your workflow and collaborate efficiently. Within cnvrg you can set access levels for users globally and for specific datsets and projects as well, making sure that your team has access to only the necessary files. It also centralizes all work and maintains the versioning to ensure the whole team is up to date.
cnvrg also is built to be completely customizable. You have complete control over all the settings both on an organization level and on an account level.
The topics in this page:
# Organization Settings
To access and change your organization's settings, click the Settings tab on the left sidebar.
Here you can change and set:
- Default Computes: This field will set the default compute of a project when created. If a Project does not have default computes set in its own settings, jobs will use the default computes of the organization.
- Install Job Dependencies Automatically: When this is enabled, your custom Docker images will automatically work with all of cnvrg's features. Read more here.
- Slack Webhook URL: The URL for yor Slack API. Used to enable experiment notifications.
- Debug Time: The default amount of minutes an experiment will stay in debug mode for. When in debug mode, the length can be extended by the user for additional 15 minute periods as desired.
- Queued Compute Wait Time: Duration to wait for the compute to be available before the job moves to next compute in the queue.
- Set max duration for: This allows you to set timeout periods in minutes for the different job types: workspaces, experiments, endpoints and webapps.
- Automatically Clear Cached Commits: Set the amount of days after which inactive caches are automatically cleared from NFS. (Only when Commit Caching is enabled).
Click Update to save any changed settings.
You can only edit max duration if you are an administrator in the organization.
# LDAP Support
cnvrg also supports authorizing users through an LDAP server. If you provide cnvrg access to your LDAP server so cnvrg can query it and authorize user access. To set this up please, contact cnvrg.io support.
# Change Account Settings
To access and update the settings of your account, click your profile's name in the top left of the side bar.
You may need to expand the sidebar if it is currently collapsed.
Here you can edit and save all the important details of your account including:
- Username: Your account's name.
- Profile Picture: A display photo for your account.
- Password: Change your password.
- Bio: A description of your account.
- Company: Your company.
- Time Zone: Used for scheduling jobs.
- Git Access Token: Your OAuth token for communicating with Git.
- VSCode Settings: Upload a Visual Studio Code settings file for use with any VSCode workspace you start.
- Default Homepage: which organization page loads on login
# Team Page
# Adding Users to the Platform and your Organization
To add new users to your organization, navigate to Team on the sidebar.
Click Add Members on the top right, add their email and select their access level and an email invitation will be sent to them.
If the email address is already affiliated with a cnvrg account, they will be sent an invite to your organization.
If the email address isn't already affiliated with a cnvrg account they will receive an invite to set up a new cnvrg account. By following the link in the invitation, the new member can create his account and will automatically be a member of your current organization.
# Access Levels
cnvrg supports many levels of access that you can set for users in your organization. This allows you to control what your users can see and what read/write permissions they have. Leveraging the permission levels leaves you in control of what your developers, analysts and business managers can see and do.
|Administrator||Can access all Datasets and Projects, manage users and change organization settings.|
|Manager||Can access all Datasets and Projects.|
|Data Scientist||Can only access Datasets and Projects that they have created or been added to.|
|Reviewer||Read only access to Datasets and Projects that they have been added to.|
|Revoke Member Access||Remove the user from your organization.|
# Other Team Settings
On the Team page you can also see each users:
- Projects (amount of Projects they are a collaborator on)
- Last Seen (the time they last logged in to cnvrg)
- Email Invite (the status of the invitation)
- Usage Limit (set the users cloud compute budget)
# Project Collaboration
While Administrators and Managers have automatic access to all Projects, Data Scientists and Reviewers must be added to Projects they are not already collaborators for.
To add another user as a collaborator on a Project, navigate to the Project's homepage. On the top right there will be a list of all the current collaborators. Click the + and you will be taken directly to the collaborator management panel for the Project. This can also be reached by going to the Project's Settings and selecting Collaborators on the left.
From here you can easily add or delete collaborators for this specific Project. This action will not affect their access to other Projects.
Data Scientists are automatically collaborators on projects they create.
# Dataset Collaboration
While Administrators and Managers have automatic access to all Datasets, Data Scientists and Reviewers must be added to Datasets they are not already collaborators for.
To add another user as a collaborator on a Dataset, navigate to the Dataset's homepage. Go to the Dataset's Settings and select Collaborators on the left.
From here you can easily add or delete collaborators for this specific Dataset. This action will not affect their access to other Datasets.
Data Scientists are automatically collaborators on datasets they create.