> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/getting-started/deployment-guides/your-first-30-days/5-customize.md).

# 5: Customize

Customize a few items so your users know communication sent via Material is legitimate.

{% @arcade/embed url="<https://app.arcade.software/share/ZJtZ2VpRb9tMI30nD1al/QNEXyfu6x69dGGrVLYKs>" flowId="ZJtZ2VpRb9tMI30nD1al" %}

### Organization Profile and Team Name

1. From Settings, click **Organization Profile**:

<figure><img src="https://content.gitbook.com/content/ksjM8NywYRSHu1IlfxdP/blobs/vDAGw8VS2t94zbwHMINv/image.png" alt="Update your logo and team name in Settings, under Organization Profile" width="375"><figcaption><p>Settings > Organization Profile</p></figcaption></figure>

2. **Update the default Team Name** to a name your org recognizes. For example, "Acme IT & Security Team". This name displays on all user-facing communication from Material.
3. Upload your organization’s logo. Max 1 MB. Use 50px x 150px (standard) or 100px x 300px (retina).
4. If you're using a [custom domain with Outlook Web Access](https://support.microsoft.com/en-us/office/add-a-custom-domain-name-071780ac-46bb-4758-b30d-39ad0aeccf42), toggle this option **on**. Add your **Domain Name**, then click **Save**. If you have multiple tenants, switch to the Microsoft tenant to see this option.

{% hint style="info" %}
You can use different logos and team names for individual accounts and groups. See [Group and Account Customization](/administration/group-and-account-customization.md).
{% endhint %}

{% hint style="danger" %}
You'll see **VIP Designation** after team and organization settings. Don't touch these just yet — we'll review them soon in [Review suggested VIPs](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/add-a-vip.md).
{% endhint %}

***

### Email Threat Support Email and Footer

1. From Settings, click **Organization Profile.**
2. The **Support Email** address is used in user-facing emails and as a point of contact for support requests. Use a single email address. If you don't enable this or enter an email, the point of contact in your emails will be `no-reply@mail.material.security`. This doesn't need to be a monitored inbox unless you want users to reply.

<figure><img src="https://content.gitbook.com/content/ksjM8NywYRSHu1IlfxdP/blobs/tCtzX5xArEZqxEBXPIiV/image.png" alt="Update your support email under settings in End User Support" width="375"><figcaption><p>Settings > End User Support</p></figcaption></figure>

3. The **Custom Footer** appears on end-user-facing emails and protection interstitials when a user might be attempting to interact with a sensitive or suspicious email. Custom footers direct end users to the proper place to receive support and build user trust
   1. Basic HTML tags are allowed.
   2. Good inclusions are Slack support channel links, resources, or security contacts.

For example:

{% code overflow="wrap" lineNumbers="true" %}

```html
<em>Problems? Join us in <a href="[Slack channel URL]">#[Slack channel]</a></em>. For all questions or concerns, please contact the Security team in <a href="[Slack channel URL]">#[Slack Channel]</a>. Thank you for helping keep [Organization Name] secure!
```

{% endcode %}

<figure><img src="https://content.gitbook.com/content/ksjM8NywYRSHu1IlfxdP/blobs/Im5ZGB0o7pQZxsxiv5Kt/image.png" alt="Add a custom footer in settings" width="563"><figcaption><p>Settings > End User Support > Custom Footer</p></figcaption></figure>

This HTML renders like this in user emails:

<figure><img src="https://content.gitbook.com/content/ksjM8NywYRSHu1IlfxdP/blobs/5N49CcCFzaK1JkYnRrid/image.png" alt="Rendered custom footer in an email" width="375"><figcaption><p>Custom Footer</p></figcaption></figure>

***

## Powered by Material branding

Optionally, show or hide the **Powered by Material** branding on your user-facing emails and pages.

{% hint style="info" %}
It's useful to leave the Material branding on because it helps end users recognize and trust the emails and pages they receive. Seeing "Powered by Material" signals that it's an official, IT-sanctioned tool rather than something suspicious and indirectly reinforces security awareness.
{% endhint %}

1. Navigate to **Settings** (the cog icon) > **End-User Support**.
2. Toggle Material branding on or off.

   <figure><img src="https://3411262179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FksjM8NywYRSHu1IlfxdP%2Fuploads%2Fo1PPnfwKQS5R226bvyL3%2Fimage.png?alt=media&amp;token=f476e688-8e50-415b-82f3-22af35ebbcf2" alt="End-User Support settings showing the Powered by Material branding toggle." width="563"><figcaption><p>Admins can show or hide Powered by Material branding in End-User Support settings.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.material.security/getting-started/deployment-guides/your-first-30-days/5-customize.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.