Onboard Salesforce Agentforce (Operator based scanning) to SaaS Agent Security to gain deep visibility and security for your
Salesforce Agentforce AI platform and apps.
Prerequisites- Ensure you onboard the Salesforce SaaS Security Posture Management connector before onboarding Salesforce Agentforce to SaaS Agent Security.
To access your Salesforce Agentforce instance, SaaS Agent Security requires
the following information, which you will specify during the onboarding process.
| Item | Description |
|---|
| Username | A Salesforce username is a unique identifier, formatted like an
email address (e.g., jane@company.com), that users
must provide to log into their Salesforce accounts. This username
must be distinct across all Salesforce organizations, both
production and sandbox environments, meaning you cannot have the
same username in two different Salesforce accounts. While it
resembles an email address, it doesn't need to be a real, working
email. Salesforce now offers a simplified login option on the login
page, allowing users to log in with their actual email address
instead of the specific Salesforce username. |
| Password | A Salesforce password is a secret string of characters that
authenticates a user's identity and grants them access to their
Salesforce account, data, and features. Users must meet their
organization's password policies, which set requirements for length,
complexity, and expiration, and the password is
case-sensitive. |
| TOTP Secret | A Salesforce TOTP secret is a unique, shared cryptographic key
that is used to set up and generate time-based one-time password
(TOTP) codes for multi-factor authentication (MFA). When you
register an authenticator app, like Salesforce Authenticator,
the secret key is exchanged between Salesforce and the app. This
allows the app to use the key, along with the current time, to
generate a unique, short-lived numeric code that verifies your
identity when you log in. |
