The Organization Settings section is available to Administrators by clicking Organization Settings from the account menu in the bottom of the left side navigation or by selecting Organization Settings from the header dropdown at the top of the Personal Settings page.
Organization Settings allow you to manage users, groups, RBAC, keys, and tokens. This page outlines every section and where in the documentation you can learn about specific tasks in Organization Settings.
Read the user management documentation to add, edit, and disable users.
Service accounts are non-interactive accounts that you can use to own application keys and other resources that are shared across your teams. Service account application keys can only be viewed once by the individual who created the key. You can use service accounts to access Datadog APIs without associating your application or script with a particular person.
To learn about default and custom roles in Datadog, read the Role Based Access Control documentation.
SAML Group Mappings
When enabled, users logging in with SAML to your Datadog account are permanently stripped of their current roles and reassigned to new roles. The SAML assertion passed on from the Identity Provider and the mappings you create determine each user’s new roles.
Users who log in with SAML and do not have values that map to a Datadog role are permanently stripped of all roles. That user may no longer log in.
To learn how to create and set mappings, read the Mapping SAML attributes documentation.
To learn how to configure SAML, read the Single sign on with SAML documentation.
This section allows you to view, copy, and revoke any API key in the list. Your API keys are unique to your organization. An API key is required by the Datadog Agent to submit metrics and events to Datadog. Read the API keys documentation for more information on creating, editing, and revoking keys.
You can filter application keys by name, ID, or owner, or click the Only My Keys toggle to only view application keys you own. Read the Application keys documentation for more information on adding and removing keys.
Client tokens are used to send events and logs from your user’s web and mobile applications. They are unique to your organization. Deleting a client token that is linked to a RUM Application causes your RUM Application to stop reporting. The process to create client tokens is similar to that for API and application keys.
Events API Emails
If your application does not have an existing Datadog integration, and you don’t want to create a custom Agent check, you can send events with email. To learn how to set up events API emails, read the Events with email guide.
The Public Sharing tab contains lists of shared dashboards and shared graphs. You can also edit your sharing settings by clicking the Enabled toggles.
The Login Methods tab shows password, Google, and SAML authentication settings. You can toggle each with the Enabled by Default dropdowns. In order to be “SAML Strict” or strict for any other type of login, disable the other login method types. You can allow per-user overrides in the User Management tab to allow users to login with another login method if needed.
The Audit Trail tab in the Organization Settings page opens a new tab to the Audit Events Explorer.
Audit Trail Settings
The Audit Trail Settings tab allows you to set the retention period of audit trails and enable archiving to other cloud storage services.
The OAuth Apps page allows you to view or manage OAuth applications in your organization.
To rename your organization, click the Edit button in the Preferences tab of Organization Settings, enter the new name, then click the Save button.
Note: Your organization name must not exceed 32 characters.
Out-of-contract retention periods for log indexes
Org Management permission can enable the out-of-contract retention periods feature for log indexes.
When enabled, users with
Modify Index permission can choose any of the 3-, 7-, 15-, 30-, 45-, and 60-day retention periods, even if it is not in the contract. This can be useful when troubleshooting a potential long standing issue or meeting compliance requirements for which customers need a higher retention period that is not part of the current contract.
Note: Using out-of-contract retention periods incur on-demand charges. If an out-of-contract retention period is often used, Datadog recommends that customers contact their account manager to have it added to their contract.
Additional helpful documentation, links, and articles: