Mandiant Advantage Attack Surface Management (MA-ASM) Account Settings include both user- and project-specific settings. This is where you can generate API keys, add integrations, and manage project membership.
Account Settings are available under the Projects and Settings menu in MA-ASM. 
The following Account Settings are available:
User
Project
The availability of each setting depends on your role (owner or member) within the selected project. If a setting is only available to project owners, that is called out for you.
Account
This category shows Basic Information associated with your account including role (Owner or Member), Full name, Email, and Organization. For more information on switching organizations, see ASM Organization Switcher.
Notifications
This setting allows you to toggle Daily Digest Emails on or off. These emails serve as a digest of new results found in your collections.
API Keys
Application programming interface (API) keys are unique identifiers used to authenticate to the MA-ASM API. An API access key is required when linking integrations. For more information on using the API, see Attack Surface Management API.
Settings
You must be the project owner to view and modify Settings.
These Project Settings allow you to edit the project Name and Icon, as well as manage project owners. 
Billing
This setting gives you information about your plan version, including the status of your plan and the expiration date.
Integrations
You must be the project owner to view and modify Integrations.
Here, you can manage various inbound and outbound Integrations. For more information about configuring specific integrations, see Integrations.
Members
You must be the project owner to view and modify Members.
This setting allows you to manage project members, including owners and groups of members. For more information, see Manage Project Membership.
Logs
You must be the project owner to view Logs.
This may also be referred to as an impersonation log.
Mandiant employees may access customer environments in an effort to provide support. Some scenarios when impersonation by Mandiant employees may prove beneficial include:
- To assist with collection configuration
- To view entities or issues specific to your environment
- To monitor ongoing support issues
Customer Service Logs are maintained so that you know when these impersonations take place. The User column provides the name of the user that was impersonated by a Mandiant employee, while the Login Date column identifies the time and date of the impersonation.
