Skip to main content
When you connect an assistant with OAuth, you decide what it may do. You make that choice on a VEXiON page, not in the AI app, so the AI app cannot widen its own access.

​
Who can connect

An assistant can connect to a business only if both are true:
  • You are an admin of that business.
  • The business is on VEXiON PRO and is active.
If none of your businesses qualify, the consent page says so and offers no business to choose. If you are an admin of several qualifying businesses, one connection can cover up to 50 of them. Each business has its own access level. After you add the server to your AI app, VEXiON opens a page with three steps.
1

Choose businesses

Tick the businesses the assistant may use. It sees only these businesses. Select all ticks every business, and the counter Businesses you can connect: N shows how many qualify. A business already connected to this app is ticked and shows a Connected badge. Businesses you cannot connect are greyed out with the reason, for example “Needs the PRO plan” or “Only admins can connect AI apps”. Click Continue (N).
2

Choose access

Pick one of the three levels below. Read only is the recommended default. The level applies to all the businesses you chose. You can change one business on the next step.
3

Review and authorize

You see the app name, each business with its access, the exact list of what the app will be able to do, and the address you will be sent back to. With several businesses the list is titled “In these businesses it will be able to, at most”. Click Authorize, or Deny to stop.
On the review step, each business has an Edit button and a Remove button. Edit opens the access step for that one business only. The others keep their access. Remove drops the business from the list. Add another business goes back to the first step. Nothing is saved until you click Authorize.

​
Connect again

Connecting an app again replaces its list of businesses. The businesses it already has are ticked from the start and show Connected. A business you untick or remove is left out on Authorize, and the app loses access to it. A business that is no longer available (you lost the admin role, or it left VEXiON PRO) is greyed out and left out too. If the ticked businesses have different access today, step 2 shows no level: Review keeps each connected business’s access and gives a new one Read only. After Authorize, the new list takes effect on the first request of the AI app. The app must make that request within 10 minutes, otherwise the authorization expires. Until then the app keeps the old access, with these differences:
  • a raise waits
  • a lowering applies at once
  • a removed business becomes read only
  • a newly added business has no access yet

​
Access levels

Whatever you choose, the assistant can always see your business name, plan and custom field definitions.

​
Customize: access per area

With Customize you choose an access level for each area. Choose at least one area above None. Sending notifications needs Write access to Customers, so that is switched on too when you allow it.
Writing also updates customers’ wallet passes and can trigger your business’s own automatic messages, for example when a reward is reached. The review step reminds you of this when you allow writing.
A tool the assistant has no access to is not shown to it at all. The tool list shows every tool that at least one of the connected businesses allows (the union over the businesses). Each business is checked on its own: a tool works in a business only if the access of that business allows it. A call for a business without that access is refused with a message that names the business. If you ask for something outside your grant, the assistant explains that it needs more access, and you can raise the level with Change access (see below).

​
Which tools each level can use

The tool list shows the area and access each tool needs. In short:
  • Read only: the 19 tools that look things up or report.
  • Read and write: all 31 tools.
  • Customize: the tools whose area you allowed.
list_businesses needs no scope, so it is available at every level.

​
See connected apps

Go to Settings > Developer > AI assistants. The tab shows the apps connected to the business you have open in the dashboard, for admins on VEXiON PRO. Each connected app shows:
  • the app name and the person who connected it
  • the access level it has in this business
  • when it was last used
  • Waiting for first use, if you authorized it but it has not made a call yet

​
Change access

Click Change access on an active row. The dialog “Change access for” the app offers the same three levels. Click Save. Only this business changes. The change applies from the app’s next request. The app is not notified in any other way.
  • A lower level applies at once.
  • A tool the app did not have before shows up when the app reloads its tool list. In practice that is a new chat in Claude or ChatGPT.
  • Only the person who connected the app can raise its access. Any other admin of the business can only lower it. They see the note “Only the person who connected this app can give it more access. You can lower it.” and get that message if they try to raise it.

​
Revoke an app

1

Open AI assistants

Go to Settings > Developer > AI assistants.
2

Revoke

Find the app and click Revoke, then confirm. The app loses access to this business right away. Other businesses connected to it keep their access.
When it was the last business of the app, the app is disconnected completely. You can connect the same app again later. Connecting again lifts the revocation and asks you to choose the businesses and the access once more. If an app is waiting for its first use and you do not want it, click Decline.

​
How fast access ends

Only the business that changes is affected. The other businesses of the connection keep working. A business that becomes unavailable (admin role lost, left VEXiON PRO) is shown as unavailable by list_businesses. A paused business stays listed, but calls are refused with the account-state message. For that minute, a call that was already allowed can still go through. To stop an assistant at once, revoke the app in AI assistants.

​
API keys

An API key has no consent screen. One key reaches one business. Its scopes are the permission. The assistant sees only the tools whose scopes the key holds. Create keys with the smallest set of scopes the agent needs, and revoke a key in Settings > Developer when you no longer need it. See Introduction.

​
What the assistant can never do

These stay out of reach whatever access you choose. They are available only in the dashboard (or, for developers, the REST API):
  • billing, plan changes and invoices
  • team members and their roles
  • API keys
  • webhooks
  • gift card balances, gift card refunds and money adjustments
  • changing a customer’s marketing consent
  • deleting cards or customers
  • changing custom field definitions
Some tools also refuse specific cases. See Tools.

​
What the AI provider sees

The assistant does not copy your data in bulk. It asks VEXiON a question, VEXiON answers, and only that answer goes to the AI app. The AI provider (for example Anthropic or OpenAI) sees:
  • your messages in the conversation
  • the results of the tools the assistant called, for example the customers it looked up or the totals of a report
Reports return counts and ids, not personal details. A customer lookup returns that customer’s profile. The AI provider handles that data under its own terms and privacy policy, not VEXiON’s. VEXiON does not control what an AI app does with what it receives. Read your provider’s data and retention settings, and remember that customer names, emails and phone numbers are personal data under GDPR. Allow Read only, or only the areas you need, when the assistant does not need to see customers. VEXiON records basic usage telemetry for the MCP server: the name of the tool, how long it took and the type of error, if any. It contains no customer data. A sign-in issued for the VEXiON MCP server is refused anywhere else, and a sign-in meant for another server is refused here. Error messages show the assistant no internal technical details and no one else’s data. Names, notes and custom field values are typed by customers or staff. The server hands them to the assistant as data, never as instructions, to limit prompt injection. Still, be careful when an assistant reads text a stranger wrote.

​
Good practice

1

Start with Read only

Most questions (reports, lookups) need no write access. Add write access only when you need it.
2

Connect only apps you trust

The consent page reminds you that VEXiON does not check what an app does with your data once you authorize it.
3

Read every preview

Check the audience and the text of a notification before you confirm. See Tools.
4

Keep tool approval on

Turn on your AI app’s tool-approval setting, if it has one, so you also see each tool call before it runs.
5

Protect API keys

Keep keys in environment variables, give each agent its own key with the fewest scopes, and revoke keys you no longer use.
6

Review the list now and then

Open Settings > Developer > AI assistants and revoke apps nobody uses.

​
Report a vulnerability

If you find a security problem, email security@vexioncards.one. Include what you found and how to reproduce it. For privacy questions about your data, contact VEXiON support.