Secured user access
To help ensure authorized access to Oracle Eloqua and personal data, Oracle Eloqua provides the ability to configure granular access controls. This enables your organization to distinguish which individuals or groups should have access to Oracle Eloqua and personal data. SSO and IP allowlisting mechanisms can also be used as an additional layer of protection to prevent unauthorized access based on your business and legal requirements.
Oracle Eloqua offers you various protections to secure user access to Oracle Eloqua and help prevent unauthorized access. Using Oracle Eloqua security configuration you can:
- Manage the password requirements such as password complexity, expiry, reuse.
- Manage login security such as idle session timeout, maximum session length, allowed failed login attempts, and a lockout policy.
- Restrict login access to Oracle Eloqua to a specific IP address range.
Learn more about security configuration.
You can enable secure user access to Oracle Eloqua by using your single sign-on (SSO) vendor. Enabling SSO allows your organization to take advantage of the security features you've already implemented with your SSO identity provider. If you are using Salesforce SSO, Oracle Eloqua provides you with a guided integration solution. Otherwise, Oracle Eloqua supports any SAML 2.0-compliant identity provider.
Learn more about Oracle Eloqua's single sign-on.
Security groups manage what users can do within Oracle Eloqua. Security groups allow granular control of user licensing, UI access, and asset permissions based on groups of users and their business role.
Oracle Eloqua provides you with default security groups. These groups align with the types of users typically accessing Oracle Eloqua data and features. You can customize or create your own security groups to align with your business needs.
Note: Customizing security groups is not available with the Basic trim.
The following default security groups are available:
- Everyone: The most basic security group that allows an authorized user to access Oracle Eloqua.
- Basic Users – Marketing: Allows access to the basic marketing features of Oracle Eloqua.
- Advanced Users – Marketing: Allows access to more advanced marketing features like microsites, forms, and automated programs
- Executive Users: Allows limited access to Oracle Eloqua marketing features, and is intended to give access to Oracle Eloqua reporting functionality.
- Active Users – Sales: Allows access to Sales team features like Profiler and Engage and the ability to send emails to contacts.
- Administrator: Allows access to all aspects of Oracle Eloqua.
Learn more about security groups.
To access Oracle Eloqua products such as Engage or Insight, you use licenses. UI access and asset permissions are then used to determine the permissions that users have to functionality available with the license.
You assign licenses to a security group and you can customize the licensing when you set up a user. The number of licenses that are available to you depends on the trim you have purchased.
Oracle Eloqua provides the following licenses:
- Marketing Platform: Provides access to the core platform. This will be the most common user license needed. If a user does not have this license and logs in, they will only have access to their user profile.
- Eloqua Engage: Provides access to Engage.
- Eloqua Profiler: Provides access to Eloqua Profiler.
- Eloqua Reporting: Provides access to Insight, Oracle Eloqua’s reporting platform.
- Eloqua Analyzer: Provides access to customize and create reports in Insight.
- Customer Administrator: Provides access to configure system defaults and security settings.
- Eloqua Sales Tools for Microsoft Outlook: Provide access to Oracle Eloqua Sales Tools for Microsoft Outlook.
Learn more about licensing.
You can manage access to the Oracle Eloqua UI using interface access and action permission settings.
- Interface access determines the pages of Oracle Eloqua that a user can access.
- Action permissions determine the access level that a user has to a page in Oracle Eloqua. For example, manage contacts or run integration rules.
Together these settings allow you to manage what pages the user can access and what UI controls are available.
Asset permissions determine what users can do with Oracle Eloqua assets. An asset is more than just emails, landing pages, and forms. Asset permission manage permissions to any object in Oracle Eloqua. Using asset permissions you can ensure that only the appropriate users can view, create, edit, and delete assets.
Assets are managed by these permissions:
- Asset creation permissions – determines the types of assets a security group can create. By default, an asset creator can change their assets.
- Asset permissions – determines the types of assets a security group can view, edit, delete, and grant others access to. By default, the asset creator can manage access to the asset.
For example, you grant marketing users access to view picklists. This allows the marketers to use the picklist in their campaigns. However, deleting or changing a picklist could impact several campaigns. So, administrators can use asset permissions to tightly manage who can change or delete the picklist, thus minimizing the impact across Oracle Eloqua.