Code entities and user roles
When setting up your Spotfire environment, you can specify that certain users or certificates should be trusted as signers in specific roles. One user might be trusted in the role of a developer, whereas another is trusted as configurator of external actions.
Code entities
The table below lists the currently available entities for which trust can be specified.
| Type | Description |
|---|---|
| visualization_mod | Spotfire visualization mods are custom
visualizations that can be used like other visualizations when creating
analyses.
Read more about mod development on the Spotfire Mods website on GitHub. Read more about visualization mods in the Spotfire Client User Guide. |
| action_mod | Spotfire action mods contain one or more scripts which can be triggered when clicking on an item in a text area or a visualization in an analysis. Read more about mod development ion the Spotfire Mods website on GitHub. Read more about actions in the Spotfire Client User Guide. |
| external_action | External actions are predefined configurations in an analysis that allow end users to affect, or send data to, external systems. Read more about actions in the Spotfire Client User Guide. |
User roles
The table below lists the currently available roles that a user might have when specifying trust.
| Type | Description |
|---|---|
| developer | A developer is typically entrusted to create various extensions to the Spotfire environment, such as visualization mods or action mods. |
| configurator | A configurator is entrusted to set up actions that can affect, or send data to, external systems. |