Appearance
Step 1: Submit your Email Template
The first step in the onboarding process is to submit a Jira ticket for your email template to be reviewed and approved by P1's Cyber team. They control the approval process for all email templates that your team can use.
Template Requirements
Please include the following information in your submission:
- Team Name: This will be used for template creation and your credentials.
- GitLab Repository Link: Provide a link to your GitLab repository.
- Impact Level: Impact Levels Needed: (IL2 Staging, IL2 Production, IL4 Staging, IL4 Production, IL5 Staging, IL5 Production).
- Point of Contact: Designate a primary contact person for the approval process.
- Email Template: Submit your complete template
- Static example:
"Hey, your account password has expired with our service. Please sign in to reset your password."
- Dynamic example:
"Hey, [ name : max character limit 10 ], your appointment at [ place: max character limit 30 ] is set for [ date: max character limit 15 ]."
- Dynamic Template Fields (If Applicable): Clearly indicate dynamic fields within your template. For each field, specify:
- Maximum Character Limit: Indicate the maximum number of characters allowed.
- Example Use Case: Describe a specific scenario where your template would be used. Include examples of dynamic field values to illustrate how they function in context.
- Static example:
- Expected Recipient Email Domains: List all expected recipient email domains (e.g., us.af.mil, email.gov, etc).
- Credential Delivery: Choose your preferred method for receiving your P1PS credentials after approval:
- DOD Safe
- IL4 Mattermost
- Custom From Email Address (Optional): If desired, indicate the custom email address you'd like to use (e.g. emails@my-company.com). Note that most *.mil from addresses are not supported, as those domains usually enforce DMARC restrictions, and all custom addresses require email verification.
Additional Requirements for Dynamic Templates:
- Justification: Explain why a dynamic template is necessary for your specific use case over a static one.
- Security Manager Approval: Obtain approval from your company's security manager before submission.
- Impact Level Compliance: Confirm that the template adheres to its intended impact level.
Need Help?
If you have any questions or require assistance, please don't hesitate to reach out on our support channel on IL2 Mattermost.