The Management page can be accessed by clicking on the corresponding tab under Settings. Note: The Management page is accessible only for users having a Manager role.
Illumina Support Access
Enable case access for our support team via a slider button to provide billing, administrative, and support services. You can also disable it afterward to ensure maximum security.
Storage
Connect a new storage, edit its details, check connection, or delete a storage. Please check out a dedicated Managing data storage article collection for instructions.
S3 credentials
Manage API credentials (an access key ID and a secret access key) used to connect to the default AWS S3 storage bucket (32.0+): create, deactivate, activate or delete.
Test Statuses
a. #### Case Statuses
Create Case statuses, remove Case statuses that haven't been in use and change order of Case statuses by drag and drop. The order will be reflected in the Case Status dropdown featured in Cases table and Individual case page Top bar.
Be sure to scroll down and click _Save_!
b. #### Stale Days
Define the number of days that must pass without the case being finalized for it to be classified as "stale" and subsequently factored into the Stale Cases statistics on the Dashboard.
Be sure to scroll down and click _Save_!
c. #### Variant Tags
Create custom Variant tags and remove Variant tags that haven't been in use. If you're using our reporting solution, please avoid using spaces in the Variant tag name.
Be sure to scroll down and click _Save_!
Test Settings
a. #### Case Labels Create, edit, and remove Case labels that haven't been in use. Once you're done, don't forget to click Save at the bottom of the Test Settings section*.*
b. #### Gene lists Create gene lists from scratch or from existing ones, edit, remove, hide, unhide, and download. Adding and removing genes to the list is only available for gene lists that haven't been in use; editing the list name is not restricted.
c. #### Enrichment kit BED files (30.0+)
Add enrichment kits defined by BED files and hide/unhide custom kits.
33.0+: Improved BED validation errors When attaching a BED file to a kit in the Management tab, the system will generate clear and actionable error messages for any exceptions that may occur.
Groups
Create and delete user groups as needed, aligning them with your case review workflow. Each user group is represented by its dedicated column in the Cases table.
Webhooks
Set up webhooks. You might need assistance from your IT team.
The My settings page can be accessed by clicking on the corresponding tab under Settings.
Add or modify your details, including: a. Full name, b. Title, c. Specialty, d. License number.
2. _Contact Information_
3. _Organization_
4. _Roles and Permissions_
Review the permissions you have been granted.
5. _Profile Picture_
Upload or change your profile picture.
The Organization Settings page (33.0+) is accessible via the dropdown menu under . Note: The Organization Settings page is accessible only for users having a Manager .
On ILMN Cloud, customers can easily associate URLs with their current workgroup by selecting from a list of predefined URL patterns. These URLs play a crucial role in organizing and accessing workgroup-specific resources.
Key Points to Remember:
URL Selection: You can choose from a set of predefined URL patterns.
Multiple Associations: A single URL can be associated with one or several workgroups.
Activation Time: After selecting the URL for your workgroup, please allow 1 to 15 minutes for the changes to take effect.
Need a Custom URL?
If you would like to create a new custom URL pattern within your domain, please reach out to our technical support team at for assistance.
Important! If you switch to a version older than 33.0, the feature will be removed from your Organization Settings, and you will need to reach out to support for platform version changes.
By default, Emedgene displays the Case ID in the "EMGXXXXXXXXX" format*.* However, you have the choice to use the Proband ID instead. Please note that the Proband ID has a visible 13-character limitation, with the remaining characters visible upon hovering.
The default page upon entering a case can be customized. You can choose between:
Click on an downward arrow icon left to the Preset's name.
Click on the ✏️_Edit_ icon;
Make the necessary changes. Editing the Preset requires basic understanding of JSON data format;
Locking the Preset prevents any user from changing it.
Click on the 🔓_Lock_/Unlock icon;
Click on Lock/Unlock in the popup window.
Click on the 🗑️_Delete_ icon;
Confirm your decision by clicking Delete in the popup window.
Note: Only unused Presets can be deleted.
In versions prior to 34.0, creating Preset groups required technical support. With 34.0+, Preset groups can be easily created by combining different Presets. Alternatively, you can upload a JSON file that defines the Presets in a Preset group. The file name and schema will be validated upon upload.
The section has two tabs:
V2 (new)
V1 (legacy)
Migrating V1 _Preset groups_** to the improved V2 methodology**
Click on Add new;
From the dropdown, select New;
Enter a name for the Preset group. Note: The Preset group can't be renamed later!
Select Presets to include in the Preset group. Click Add after selecting each Preset;
Drag and drop Presets to change the order;
Click on Save.
Click on Add new;
From the dropdown, select From file;
From the file browser, select a JSON file that defines a Preset group;
The system will thoroughly validate the file;
If validation is successful, a Preset group will be created. Any underlying Presets that are missing from your organization will be added as well.
Click on an downward arrow icon left to the Preset group's name.
Click on the ✏️_Edit_ icon; 2a. Add Presets to the group as needed. Select Presets to include in the Preset group from the dropdown. Click Add after selecting each Preset; 2b. Remove Presets from the group as needed. Click on the 🗙_Remove_ icon on right to the right of the Preset name. 2c. Drag and drop Presets to change the order;
Click Save.
Click on the 👁️_Hide/Unhide_ icon.
Click on the ⬇️_Download_ icon.
Click on the ↩️_Revert_ icon to undo the migration.
Click on the dropdown arrow;
Select the Preset group;
Click Save.
Select a platform version for your organization from the options available in your region. Please allow 1-15 minutes for changes to become active. Keep in mind that this selection will not alter your pipeline version, only the software version. To change a pipeline version please contact .
- default option;
*;
*;
.
You can customize the default order of . Just rearrange the columns by dragging and dropping them to your preferred sequence.
Here you can review and manage organization filter .
Upon clicking on Add new, you will be redirected to Analysis tools page where you can .
Click Save. The software will perform schema validation on the edited Preset. Note: you can modify the Preset's content but not its name. Note: the Preset can't be edited if it's .
Here you can review and manage filter .
Here you can create (/, , , and your organization's Preset groups.
Here you can and legacy Preset groups.
Legacy Preset groups can be migrated to the new methodology via two simple steps: the Preset group JSON file in the V1 (legacy) tab, then it on the V2 (new) tab.
This is the second step in the of the V1 (legacy) Preset group, after you have the Preset group JSON file.
When you hide a Preset group, it will no longer appear in the Preset groups list offered at case creation ( ).
Note: A cannot be hidden.
This is the first step in the of the V1 (legacy) Preset group to V2 methodology. A Preset group file contains preset names and the filters used to define each Preset in JSON format.
If a V1 Preset group that has undergone is set to revert, the corresponding V2 Preset group will be deleted.
Note: If a migrated Preset group has been assigned as , it cannot be reverted.
You can set a Preset group as default. The case is assigned to the default Preset group if no Preset group is selected or the default value is selected in the Preset group selection step.
Note: A default Preset group cannot be and cannot be .