Licence & Plan Management

REDA AI supports two ways to fund AI processing. AI included uses REDA credits. Bring your own AI uses your organisation’s own provider account: you pay the provider directly and REDA takes no share of that bill. REDA AI supplies the orchestration, agent configuration, tools, permissions and usage reporting inside Salesforce in both models.

Use this guide to activate your licence and configure the appropriate model. For current subscription prices, plan limits, trial terms and top-up options, visit REDA AI pricing. The website is the source for commercial information; this Help Center explains administration and operation.

Understand your funding model

Before you begin

Open App Launcher → REDA AI → REDA AI Admin. You need the REDA AI Admin permission set. Connection management also requires Manage AI Connections, included in that set. Use the key issued for the correct Salesforce organisation and environment.

For Bring your own AI, have an active provider account, a permitted API key and access to the model you intend to use. Review your provider’s processing, retention and billing terms. Do not paste provider keys into an agent prompt or a support message.

Create and test an AI Connection

An AI Connection is a reusable reference to a provider account. Credentials are kept in your Salesforce credential store, separately from agent instructions. Agents select the connection; they do not store the API key.

1. In REDA AI Admin → AI Connections, select New Connection. Enter a Connection Name, Provider, Provider API Key and Default Model, then select Create Connection. Choose from the supported models shown for that provider.
2. Follow the completion screen: Setup → Named Credentials → the created credential → Edit, then enable Enabled for Callouts.
3. Open Setup → External Credentials → the created credential. Grant its Default principal through External Credential Principal Access on a permission set assigned to each user or automation identity that will use the connection.
4. For website guests and portal users, also grant Read on User External Credentials through the relevant permission set. Give access only to identities intended to use that connection.
5. Return to AI Connections, select Test and confirm that the connection authenticates and the model answers. Then select Activate and Set as Default on the intended organisation default.

The organisation default supplies admin AI tools, document processing and agents that inherit it. Set an active default connection with a supported default model before activating customer-account funding. A separate Remote Site Setting is not required for this customer connection: it uses the Named Credential.

If your administrator already maintains the credentials, use Register Existing Credential and provide the requested Named Credential and External Credential developer names. Apply the same access and test checks.

Choose the account and model for each agent

1. Open REDA AI → Agent Definitions → your agent.
2. In AI Account, choose an AI Connection or Use organisation default.
3. Choose a supported Model or Connection’s default model. Check the supported Deep Reasoning levels and any web-search warning, then save.
4. Test the agent’s actual workflow under its intended user identity, including documents, tools and external channels where used. A successful administrator connection test does not establish access for other users.

Different agents can use different connected providers and models. Provider capabilities vary. Processing Tier remains the model-selection control for AI included; the AI Account selections take effect only in customer-account mode.

Activate your licence

In REDA AI Admin → License & Credits, paste the REDA-issued licence key and select Activate Key. For Bring your own AI, prepare and test the default connection and active agents first. If readiness validation identifies a missing connection or model, correct the named item and retry; the existing licence remains active if the new key is refused.

Activate Free Tier starts the AI-included evaluation. To evaluate Bring your own AI, contact REDA for the appropriate key; your provider’s own charges still apply. See pricing and evaluation terms for current details.

Read Plan Details after activation. It shows the entitlement issued to your organisation, including usage against the agent, prompt, custom-tool and MCP-agent limits. MCP connects selected agents to an external AI assistant. A limit shown as Unlimited does not remove Salesforce or provider limits.

Monitor usage without confusing it with billing

Use License & Credits for current and historical usage, and AI Conversations for the individual conversation’s Funding Mode, AI Connection and AI Model. The Customer AI Account list view helps find customer-funded conversations.

For Bring your own AI, metered credits are a usage measure, not a provider invoice or a monetary estimate. Check the provider’s console for its bill. Your own per-user and per-channel limits still apply, alongside Salesforce limits and provider quotas. The REDA allowance, low-balance top-ups and rollover apply to AI included only; the Credit Period’s Consumed Credits balance excludes customer-funded usage.

Check access after an upgrade

On an existing installation, review layouts, record pages and client-owned permission sets after upgrading. In Setup → Object Manager → Page Layouts, add the AI Account fields to Agent Definition and AI Conversation, and Funding Mode and AI Usage Details to AI Credit Transaction. Conversation and transaction audit fields should be read-only for ordinary users.

• Agent Definition: AI Connection; AI Model Profile.
• AI Conversation: Funding Mode; AI Connection; AI Model.
• AI Credit Transaction: Funding Mode; AI Usage Details.

If you use a custom Agent Definition Lightning page, add REDA AI Agent Model Selector in Lightning App Builder. The packaged page includes it. Assign the updated packaged permission sets, or grant equivalent object and field access through your own sets. Administrators managing connections need Manage AI Connections; ordinary internal users need Read access to the AI Connection records and relevant fields. Check the AI Conversations views and their columns in your subscriber org rather than assuming an upgrade has changed existing views.

Change a plan, account or model

Contact REDA for a plan or funding-model change, then activate the issued key. Creating a connection while using REDA credits does not switch your organisation automatically.

Changing the effective connection, model or funding mode means affected conversations need a new conversation. Tell users before making the change and check queued work. Use Rotate Key to replace a provider credential; every agent using that connection uses the new key. Test it afterwards. Do not delete a connection that is the organisation default or is still assigned to an agent.

Expiry and renewal

A valid REDA licence is required in both funding models. Paying your provider does not renew the REDA subscription. Keep the billing contact current, arrange renewal with REDA and review the effective dates in Plan Details.

Apply a renewed key

Activate the renewal key in License & Credits, then verify the status, funding model, dates and issued limits. For AI included, existing unexpired redeemed top-ups retain their original expiry through an ordinary renewal.

Sandbox and production

Keep each environment’s licence and provider connections separate. Test the planned account, model, permissions and workflows in the appropriate sandbox before enabling them in production.

Keep the right contacts and controls

Maintain the billing contact in the Admin Console. For AI included, monitor credit balance notifications. For Bring your own AI, monitor provider quota and billing notifications as well as REDA usage reports and your configured limits.

Troubleshooting

• Callouts blocked: enable the Named Credential for callouts.
• No credential access: check External Credential Principal Access for the actual running identity, and User External Credentials Read for guest/portal users.
• Provider rejects the key: check account access, model availability and the provider key; rotate and test it.
• No organisation default: activate a valid connection, select its default model and set it as the organisation default.
• Unsupported model or reasoning level: use a model available for that provider and a supported Deep Reasoning level.
• Scheduled Flow fails at a callout: configure the REDA AI action to Always start a new transaction.

Where to go next

See How Credits Work, Configuring Agent Settings and Data Security. For commercial choices, use the REDA AI pricing page.