Company Details
Secureframe offers a wide variety of Settings to ensure each customer has enabled the specific features and confirations needed for their compliance objectives.
Review each tab to fully understand the settings available based on your package.
This section is very important because anything denoted with a red * will auto-populate portions of the platform like Policies with this specific information provided. If populated, this will save you many hours of manual work and ensure consistency.
To add your company details, please take the following steps:
Maneuver to Company Settings, by clicking your Avatar in the top right corner and select Company Settings
Fill in your company information in the Company Details tab (e.g. company address, company phone number, Year founded, etc.).
Year founded should reflect the history of the business, not only the date of the current legal entity. If you restructured (for example S Corp to C Corp) but kept the same services, customers, and team, use the original founding year, and note both the original year and the new entity year when you can. See the FAQ below for restructure guidance.
You can return to this page at any time and edit this information.
Configurations
This settings pages will capture Billing Info, Key Personnel such as Information Security Managers, enabling features like Comply AI or SecurityScorecard.
Billing Information - set your Billing email, EIN and VAT.
Key Personnel - Assign your Information Security Manager and Board of Directors if applicable.
Labs - Enable Comply AI to access AI-powered capabilities to enable faster, more informed decision making across the entire platform. (Risk, Vendors, Questionnaires, Tests, and more)
SecurityScorecard - Enable to automatically assign a security ratings (A-F) to companies based on various risk factors, helping you more easily assess vendors, partners, and third parties. This rating will be displayed on your dashboard. Learn more about our SecurityScorecard partnership here.
Session Timeout - Log users out when they are inactive for a specific amount of time.
Audit Log
The Audit Log provides a detailed, time-stamped record of actions taken across your Secureframe instance. You can view which users made changes, what objects were affected (like users, vendors, or exports), and what fields were updated. Use filters or the search bar to quickly find specific activities and maintain transparency across your organization.
The account audit log in the UI filters out entries generated by Secureframe employees so you only see customer-account activity.
Authentication Settings
Authentication settings will be an important section to review for Admins who want to control alternate sign-in connections for specific domains.
Click here to get started with Understanding Domain Claims, SSO, and OAuth
SCIM Settings
By enabling SCIM provisioning, you can configure a push-based directory sync from your identity provider (idP) to Secureframe. User and user updates (e.g. active status) are pushed to Secureframe in near real-time.
Click here to get started with SCIM Provisioning
API Keys
If you wish to use our API Developer Portal to automate compliance workflows, fetch audit data, or manage users programmatically, the Developer Portal gives you the resources to extend Secureframe’s capabilities.
You will need to establish an API key here in the settings first.
Click here to get start with our Developer Portal (API)
Note: Custom integrations can also create an associated API key on this page (often named {integration name} API Key), scoped to that custom connection. Revoke keys you no longer need.
Email Logs
Email Logs give company admins visibility into the automated emails Secureframe sends to users (such as onboarding invites or task notifications) and vendors, helping ensure nothing slips through the cracks. Logs are available for emails generated on or after March 17, 2025.
Click here to read more on Email Logs
Frequently Asked Questions (FAQ)
Why don’t I see Secureframe employee activity in the account audit log?
The account audit log in the UI filters out entries generated by Secureframe employees so you only see customer-account activity.
Our business moved to a new legal entity (for example S Corp to C Corp). Which Year founded should we use?
Year founded reflects the history of the business, not only the formation date of the current legal entity.
If it is the same business (same services, customers, and team) under a new corporate structure, use the original founding year. Prefer noting both the original founding year and the year the new entity was formed.
Your SOC 2 report will still name the legal entity under audit (for example the C Corp).
Use the new entity year as Year founded when ownership changed, or when the prior entity still operates as a separate business.