Settings

Manage your organization and user settings in ion

User settings

Click the settings cog in the main sidebar of ION. Clicking into the User submenu, you can modify your user settings. This includes your avatar and your name. Setting these will help your team identify you throughout ION.

Organization settings

Organization admins can modify the organization's settings, including the organization's avatar and name. It also lets you set up custom attributes, the issue review process, and more.

• General Settings

  Here, you can update your company name and your ICON. You'll have to link to an internet image for now, as ION does not support a direct image upload. You'll also see the number of members your environment has, and you can update your sidebar color as well.

• DateTime

  Here, you can update the way that dates are reflected in ION

• Allowed Domains

  Here, you can update who and which domains can access your ION environment. There is also a switch to flip on our end (a double check for extra security), which allows us both to control who is in each environment. If you want to add another domain to your environment, please reach out via email to [e-mail].

All the other organizational settings allow you to add custom attributes for the different entities in ION.

Members and roles

As an organization admin, you can set the roles for the members of your company using ION. Admins can add "engineer" or "technician" roles to users. By default, the "engineer" role allows users to create and modify procedures, while the "technician" role allows the user to execute and complete runs. If you want a user to be able to do both, you can set both "engineer" and "technician" roles, and you can also add your own roles as desired. Admins can also give other users admin permissions. See more in the role based access control section.

Notifications

Here is a list of notifications emmitted by ION. Currently, ION supports email notifications.

• Review requested: If you are a reviewer on a procedure, you are notified

• Run assigned: If you are assigned to a run, you are notified

• Run failed: If you created a run, and a step fails, you are notified