/
JEMHC configuration visibility

JEMHC configuration visibility

 

Global vs Project scoped entities

JEMHC can be accessed as a Global admin from the global Apps screen, or as a Project admin from a Project settings page. The data available depends on what JEMHC page you are trying to access.

  • Global entities are visible publicly, meaning the JEMHC administrator, plus any project admin, can view this data.

  • Project scoped entities are visible to the JEMHC administrator, plus project admins of the selected project.

 

This configuration includes:

  • Profiles and Profile auditing

  • Exclusions

    • By Subject

    • By Sender

    • By Recipient

    • By attachment fingerprint

    • By URL

    • Outbound email recipients

    • By content type, size and filename

  • Test cases

  • Notifications

    • Images and static resources

  • Auditing

    • Inbound messages

    • Events and failed events

    • Outbound messages

 

Entities with multiple project scope

Some JEMHC configuration can be set up in the context of multiple projects. These include:

  • Templates

  • Profiles

 

For templates, in order for a project admin to view this data, the configuration must be global or project scoped to a project the project admin has access to.

For profiles, in order for a project admin to view this data, the admin must have access to every project in the profile scope.

 

Admin restricted Testcases

As testcases can contain sensitive data, testcases can be configured with the existing global or project scope, but also support configuration to be scoped to admin only.

By configuring a testcase to be admin only, the testcase becomes visible only to JEMHC administrators. Project admins can only view global testcases, or testcases scoped to the project that the project admin has access to.

 

How to grant project level access to JEMHC configuration

As a Project admin, if you lack access to a project, e.g. SCRUM, any JEMHC configuration for SCRUM will not be visible to you.

You will need to reach out to your JEMHC administrator to re-configure the data, changing the entity scope to global, or re-selecting another project.

For Profiles, the admin must have access to all projects in the profile mappings. If this is not desired, the JEMHC administrator can create a new profile and split out mapping configuration, creating a new profile containing only scoped projects that the project admin can view.