How To: Add a Mail Group in SessionGuardian

Follow
    Applies to:
  • SessionGuardian
Deployment model:
  • Hybrid
  • Version Affected: All Versions

     

    Overview

    This article explains how to create a custom mail group (distro email) for a project in SessionGuardian, so you can send project communications to a specific subset of members instead of the whole project. Unlike a project's default distro email (for example, all@sandbox.securereview.com), which reaches every project member, a custom mail group lets you reach just the members you add to it.

     

    Add a Mail Group

    1. Search for the project using CTRL+F.
    2. Click Actions, then select Add Mail Group.
    3. In the first field, enter the desired distro name (for example, qa-team).

      The Add Mail Group dialog with a distro name entered in the first field, which will be appended with the project's email domain.

    4. In the second field, enter the SessionGuardian email address of a project member, then click Add email addresses.

      The Add Mail Group dialog with a member email address entered in the second field and the Add email addresses button highlighted in red.

    5. Repeat the previous step until all required members are added.
    6. Click Submit to finalize the distribution group.

      The Add Mail Group dialog with a member email address added to the list and the Submit button highlighted in red.

    The new distro email, for example qa-team@sandbox.securereview.com, can now be used for team-specific communication.


     

    Special Considerations

    This feature only supports adding internal project members -- external users or email addresses cannot be added. Each custom mail group functions as its own communication hub for the members assigned to it.


     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.