TINA AI, from zero to hero
Everything you need to use AI with TINA: choose and set up your AI provider, turn on the TINA AI Assistant and ARIA AI Reports, connect TINA to Claude or ChatGPT through the TINA MCP, and put it to work safely.
Version 1.3 · Updated 19 November 2026
Level 0 · Start here
Welcome to TINA AI
TINA AI brings artificial intelligence into your daily work with TINA, the travel ERP from dcs plus. You can use it in three ways:
TINA AI Assistant
A chat inside TINA. Ask questions about your data, run quick analyses, and create or update records such as customers, suppliers, invoices and payments, always with a preview before anything is saved.
ARIA AI Reports
Build pivot reports in TINA by describing what you need in plain language, instead of configuring columns and filters by hand.
TINA MCP
Connect TINA to Claude or ChatGPT. Your team works in the AI app they already use and looks up, analyzes and updates TINA data from there.
How to use this guide
The guide takes you from zero to confident daily use, one level at a time. Use the menu to jump to the part you need.
| Level | What you do | Who usually does it |
|---|---|---|
| 0. Start here | Understand what TINA AI is and which setup you need | Decision makers, project owner |
| 1. Set up your AI provider | Create your company account with Anthropic (Claude) or OpenAI (ChatGPT), and your API keys | IT, finance, data protection officer |
| 2. Turn on AI in TINA | Activate the AI Assistant and ARIA AI Reports, and connect the TINA MCP | TINA power user, AI app admin |
| 3. What TINA AI can do | See everything the AI can do in TINA, with an example for each area | Every user |
| 4. Use cases | Follow step-by-step scenarios for everyday tasks | Every user |
| 5. Run it like a pro | Tips for great results, security, troubleshooting and answers to common questions | Every user, admins |
Built for safe changes
Whenever TINA AI changes data, it follows the same pattern: it prepares a draft, shows you a preview, and saves only after you confirm. It always acts as the signed-in user, so your existing TINA roles and permissions still apply.
Level 0 · Start here
What you need
TINA AI uses an AI provider that you choose and contract directly: Anthropic (Claude) or OpenAI (ChatGPT). Depending on the features you want, you need an organization, an API key, or both.
| You want to use | You need | Why |
|---|---|---|
| TINA AI Assistant | An API key | TINA calls the AI model in the background, on your account |
| ARIA AI Reports | An API key | Same as above |
| TINA MCP | An organization (company workspace) | Your staff work in Claude or ChatGPT, which connects to TINA |
| All of the above | Both | They are separate accounts with separate billing |
Organization and API key: two accounts, two bills
An organization is your company's workspace for your staff in Claude (Team or Enterprise) or ChatGPT (Business or Enterprise). You pay per seat. An API key belongs to a separate developer account (Claude Console or OpenAI API Platform) that TINA uses on its own. You pay per use. A seat subscription does not include API usage, and API credit does not give your staff seats. You can even choose different providers for each.
Why the accounts belong to you
You create and own these accounts yourself, directly with the AI provider. This is a data-protection choice:
- You hold a direct contractual and data-processing relationship with the provider, including its data processing addendum.
- Neither provider trains its models on your business data by default.
- You decide who has access, which features are on, and how much you spend.
- You can remove a user, or revoke a key, at any time without going through dcs plus.
- Your AI traffic is attributable to your organization alone.
dcs plus does not create, own or manage AI accounts for customers, and never pools customers under a shared account or key.
Who does what
- Your IT or AI owner creates the organization and becomes its owner.
- Your system administrator sets up single sign-on and makes TINA reachable for the MCP, if needed.
- An API admin creates the developer account and API keys.
- Your finance team approves the payment card and checks billing details and VAT.
- Your data protection officer approves the setup and records the provider as a processor.
- Your TINA power user activates the AI features in TINA, or asks dcs plus to do it.
Level 1 · Set up your AI provider
Choose your AI provider
TINA AI works with Claude, from Anthropic, and with ChatGPT and the OpenAI models, from OpenAI. Both give you the same TINA MCP capabilities. The differences are in plans, data location and cost control.
| Anthropic (Claude) | OpenAI (ChatGPT) | |
|---|---|---|
| Organization plans | Team (2 to 150 users) or Enterprise | Business (from 2 users) or Enterprise |
| Recommended plan | Team | Business |
| Adds TINA MCP for the whole company | Owner, in Organization settings | Admin or Owner, as a published custom app |
| Single sign-on | Team and Enterprise | Business and Enterprise |
| Data stored in Europe | Not available directly | Enterprise workspaces and eligible API projects |
| API account | Claude Console, one workspace per product | OpenAI API Platform, one project per product |
| API spend limits | Enforced per workspace | Project budgets alert; the organization budget enforces |
| Payment | Card; invoicing on Enterprise | Card; invoicing on Enterprise |
How to decide
If your staff already prefer one of the two apps, start there. If you need customer data stored in Europe, plan for ChatGPT Enterprise, or check the options with your data protection officer before you start. For the TINA AI Assistant and ARIA AI Reports, confirm through the dcs plus support portal which provider your TINA version supports before you create an API key.
Then follow the two steps for your provider:
- Claude: Create your Claude organization and Create your Claude API keys
- ChatGPT: Create your ChatGPT workspace and Create your OpenAI API keys
Skip the step you do not need, using the table in What you need.
Level 1 · Set up your AI provider
Create your Claude organization
Your company's Claude workspace for staff, on a Team or Enterprise plan. You need it for the TINA MCP in Claude.
| Team | Enterprise | |
|---|---|---|
| Who it is for | Companies of 2 to 150 users | Larger companies, or stricter compliance needs |
| Organization-wide connectors (TINA MCP) | Yes | Yes |
| Single sign-on | Yes | Yes |
| Automatic provisioning (SCIM) | No (just-in-time only) | Yes |
| Custom roles, custom data retention | No | Yes |
| How to buy | Self-serve | Self-serve or through Anthropic sales |
dcs plus recommends the Team plan for most customers. Seats come as Standard or Premium; Premium includes five times the usage. Start most users on Standard.
Before you start
- A business email address for the person who creates the organization. That account becomes the Primary Owner. Consider a company-controlled account, such as a shared IT mailbox, so the organization does not depend on one person.
- At least one more person who will be an Owner.
- A company payment card, legal name, billing address and VAT number.
- The number of seats and the email domains your users sign in with.
- For single sign-on: access to your DNS settings and your identity provider.
- Approval from your data protection officer.
Step 1. Create the organization
- Go to
claude.ai/loginand sign in with the business email address of the future Primary Owner. - Follow the prompts and select the Team plan. If that address already has a Claude account, go to
claude.ai/upgradeinstead. - Name the organization after your company. For Enterprise, buy self-serve or contact Anthropic sales.
Step 2. Set up billing
- Choose monthly or annual billing, and how many Standard and Premium seats you need.
- Enter your company card, billing address and VAT ID.
- To show your company name on invoices, go to Organization settings → Billing, select Use a different name on invoices and enter it in Bill to.
Step 3. Assign roles
Give the Owner role to at least two people. Owners add connectors such as the TINA MCP, manage billing and change roles. Admins invite and remove members. Users use Claude.
Roles and permissions in detail
| Permission | User | Admin | Owner | Primary Owner |
|---|---|---|---|---|
| Use Claude, chats and projects | ✓ | ✓ | ✓ | ✓ |
| Invite and remove members | ✓ | ✓ | ✓ | |
| Add connectors and enable features | ✓ | ✓ | ||
| Add or remove Admins and Owners, change roles | ✓ | ✓ | ||
| Manage billing, seats and invoices | ✓ | ✓ | ||
| Transfer the Primary Owner role | ✓ |
Your organization has exactly one Primary Owner, who uses one of your seats. Owners cannot remove themselves; another Owner must do it. On Enterprise you can also create custom roles for groups.
Step 4. Invite your members
In Organization settings → Members, invite each person by email and set their role and seat type.
Step 5. Secure sign-in (recommended)
In Organization settings → Organization and access, verify your email domain with a DNS record, set up SSO with your identity provider, and choose invite-only or just-in-time provisioning. Test with one user first.
Step 6. Control usage and spend
In Organization settings → Usage, leave extra usage off to keep a fixed cost per seat, or turn it on with an organization-wide monthly spend limit.
Step 7. Review data settings
Anthropic does not train on Team and Enterprise data by default. Add Anthropic to your record of processing activities and keep its Data Processing Addendum with your contracts.
Checklist: is your organization ready?
| Item | Where to check |
|---|---|
| The organization is on a Team or Enterprise plan | Organization settings → Billing |
| The Primary Owner is a company-controlled account | Settings → Account |
| At least two people have the Owner role | Organization settings → Members |
| Every user who will use the TINA MCP has a seat | Organization settings → Members |
| Billing details, VAT ID and invoice name are correct | Organization settings → Billing |
| Extra usage is off, or on with a spend limit | Organization settings → Usage |
| SSO is set up, if your company uses it | Organization settings → Organization and access |
| Your data protection officer has approved the setup | Internal |
Next step
Your organization is ready for the TINA MCP in Claude. If you want dcs plus to activate the MCP endpoints in TINA for you, open a ticket in the dcs plus support portal with your plan, the name of the Claude Owner who will add TINA, and the TINA instances to connect, for example production and test.
Level 1 · Set up your AI provider
Create your Claude API keys
A Claude API key lets TINA call Claude in the background for the TINA AI Assistant and ARIA AI Reports. It lives in a separate developer account, the Claude Console, billed per use from prepaid credit.
Check first
Confirm through the dcs plus support portal that your TINA version accepts a Claude API key before you buy credit.
What an API key is
- Programmatic. It authenticates server-to-server calls from TINA to Anthropic. No person signs in.
- Secret. Anyone who holds it can spend against your account. Treat it like a password. Claude keys start with
sk-ant-. - Usage-billed. You pay per token processed, with no per-user license.
- Prepaid. When your credit runs out, the AI features stop until you top up.
Use a service account key. A personal key stops working when the person who created it leaves your organization, which would switch off your AI features. A service account key keeps working.
Step 1. Create your Claude Console organization
- Go to
platform.claude.comand sign up with a shared company email address. - Enter your organization's legal name and verify your email.
- Under Settings → Members, invite a second Admin.
Step 2. Set up billing
- In Settings → Billing, add your company card and billing details, including your VAT number.
- Buy a small initial credit balance. Credits expire one year after purchase and are non-refundable.
- Decide about auto-reload, and set an organization-wide monthly limit under Spend limits.
Step 3. Create a workspace for TINA
- In Settings → Workspaces, click Create workspace and name it, for example
dcs plus TINA. - Check the data location fields before you save: a workspace's data location cannot be changed later.
Do not use the Default Workspace for production: it cannot have a spend limit.
Step 4. Create a service account and its key
- In Settings → Service accounts, create a service account, for example
dcs plus integrations, and add it to the TINA workspace. - In Settings → API keys, click Create key. Name it, for example
dcs plus TINA production, choose an expiration that matches your rotation policy, and link it to the service account and the TINA workspace. - Copy the key into your password manager or secrets vault. It is shown only once.
Step 5. Set a limit on the workspace
In Spend limits, set a monthly limit for the TINA workspace with email notifications at, for example, 50% and 80%. Anthropic enforces it: requests stop when the limit is reached.
Tip
TINA can use a separate key for each AI feature, so you can track cost and rotate keys per feature. Create one key per feature if you want that level of control.
Next step
Open a ticket in the dcs plus support portal. The Customer Experience team confirms whether you add the key yourself in TINA's settings or dcs plus adds it for you, which models each AI feature uses, and the secure channel to use. Never email a key in plain text. Details: Turn on the AI Assistant and ARIA AI Reports.
Level 1 · Set up your AI provider
Create your ChatGPT workspace
Your company's ChatGPT workspace for staff, on a Business or Enterprise plan. You need it for the TINA MCP in ChatGPT.
| Business | Enterprise | |
|---|---|---|
| Who it is for | Companies from 2 users, self-serve | Larger companies, or stricter compliance needs |
| Custom MCP apps (TINA MCP) | Yes, created and published by admins and owners | Yes, with role-based access per app |
| Single sign-on | Yes (SAML or OIDC) | Yes |
| Automatic provisioning (SCIM) | No | Yes |
| Data stored in Europe | No | Yes, chosen when the workspace is created |
| How to buy | Self-serve, card payment | Through OpenAI sales |
dcs plus recommends the Business plan for most customers. If you need data stored in Europe, start on Enterprise: data residency is set when the workspace is created. Seats come as Standard or Premium, with at least two paid seats.
Before you start
- A business email address for the person who creates the workspace. That person becomes the first Owner.
- At least one more person who will be an Owner.
- A company credit or debit card. Invoice billing requires Enterprise.
- The number of seats and the email domains your users sign in with.
- For single sign-on: access to your DNS settings and your identity provider.
- Approval from your data protection officer.
Step 1. Create the workspace
- Open the ChatGPT Business signup page and sign in with the business email address of the future Owner.
- Choose Business, review seats, billing frequency and payment, and complete checkout.
- Name the workspace after your company. For Enterprise, contact OpenAI sales.
If your company already has a Business workspace, ask its Owner for an invitation instead: only one workspace can verify your email domain.
Step 2. Set up billing
Choose monthly or annual billing and your seats, enter your company card and billing address, and check that your company name and tax details are correct. Set the default seat type in Workspace settings → Billing.
Step 3. Assign roles
Give the Owner role to at least two people. Owners manage billing, roles and identity. Admins and Owners manage apps, including the TINA MCP app. Members use ChatGPT.
Roles and permissions in detail
| Permission | Member | Admin | Owner |
|---|---|---|---|
| Use ChatGPT and create GPTs | ✓ | ✓ | ✓ |
| Invite members | ✓ | ✓ | ✓ |
| Remove members | ✓ | ✓ | |
| Manage apps, including custom MCP apps | ✓ | ✓ | |
| Invite Admins and Owners, change roles | ✓ | ||
| Manage billing, seats and invoices | ✓ | ||
| Manage identity and SSO | ✓ |
An Analytics Viewer role is also available for people who only need workspace analytics.
Step 4. Invite your members
In Workspace settings → Members, select Invite member, enter email addresses or import a CSV, and choose each person's role and seat type.
Step 5. Secure sign-in (recommended)
In Workspace settings → Identity & Provisioning, verify your email domain, then set up SSO with SAML or OIDC. Test with one user first.
Step 6. Control usage and spend
Workspace credits are optional and only unblock members who reach their limits. If you buy them, set Usage Alerts in Workspace settings → Billing.
Step 7. Review data settings
OpenAI does not train on Business or Enterprise data by default. Add OpenAI to your record of processing activities and keep its data processing addendum with your contracts.
Checklist: is your workspace ready?
| Item | Where to check |
|---|---|
| The workspace is on a Business or Enterprise plan | Workspace settings → Billing |
| At least two people have the Owner role | Workspace settings → Members |
| The person who will add the TINA MCP is an Admin or Owner | Workspace settings → Members |
| Every user who will use the TINA MCP has a seat | Workspace settings → Members |
| Billing details and invoice name are correct | Workspace settings → Billing |
| No credits, or credits with usage alerts | Workspace settings → Billing |
| SSO is set up, if your company uses it | Workspace settings → Identity & Provisioning |
| Your data protection officer has approved the setup | Internal |
Next step
Your workspace is ready for the TINA MCP in ChatGPT. If you want dcs plus to activate the MCP endpoints in TINA for you, open a ticket in the dcs plus support portal with your plan, the name of the ChatGPT Admin or Owner who will add TINA, and the TINA instances to connect, for example production and test.
Level 1 · Set up your AI provider
Create your OpenAI API keys
An OpenAI API key lets TINA call OpenAI models in the background for the TINA AI Assistant and ARIA AI Reports. It lives in a separate developer account, the OpenAI API Platform, billed per use from prepaid credit.
What an API key is
- Programmatic. It authenticates server-to-server calls from TINA to OpenAI. No person signs in.
- Secret. Anyone who holds it can spend against your account. Treat it like a password. OpenAI keys start with
sk-. - Usage-billed. You pay per token processed, with no per-user license.
- Prepaid. When your credit runs out, the AI features stop until you top up.
Use a service account key. A key that belongs to a person stops working when that person leaves your organization. A service account belongs to the project and keeps working.
Step 1. Create or sign in to your API Platform account
- Go to
platform.openai.comand sign up with a shared company email address. If you already use it for ChatGPT, sign in with the same credentials: the sign-in is shared, but billing is separate. - Enter your organization name, verify your email and phone, and invite a second Owner.
Step 2. Set up billing
- In Settings → Billing, add your company card and billing address, and your VAT number.
- Buy a small initial credit balance (minimum 5 USD). Credits expire one year after purchase and are non-refundable.
- Decide about auto-recharge, which is on by default, and set the organization budget at
platform.openai.com/settings/organization/limits. It blocks requests once reached.
Step 3. Create a project for TINA
- In Settings → Projects, click Create project and name it, for example
dcs plus TINA. - If you need processing in Europe and a region option is shown, select Europe (EEA + Switzerland) now. It cannot be changed later.
Do not use the Default project for production.
Step 4. Create a service account and its key
- In the project's Members settings, create a service account, for example
dcs plus TINA production. - OpenAI shows the key once. Copy it into your password manager or secrets vault.
- Keep the default key permissions unless dcs plus gives you a narrower list.
Step 5. Set limits on the project
In the project's Limits, set a monthly budget with alerts at, for example, 50%, 80% and 100%, and allow only the models TINA needs. A project budget is an alert, not a hard stop: keep it below the organization budget from step 2.
Tip
TINA can use a separate key for each AI feature, so you can track cost and rotate keys per feature. Create one key per feature if you want that level of control.
Next step
Open a ticket in the dcs plus support portal. The Customer Experience team confirms whether you add the key yourself in TINA's settings or dcs plus adds it for you, which models each AI feature uses, and the secure channel to use. Never email a key in plain text. Details: Turn on the AI Assistant and ARIA AI Reports.
Level 2 · Turn on AI in TINA
Turn on the AI Assistant and ARIA AI Reports
The TINA AI Assistant and ARIA AI Reports run inside TINA and use your own API key (see Level 1). The AI Assistant is part of the standard TINA product from TINA 4.0.
TINA AI Assistant
A chat inside TINA, as a side panel or a full page with conversation history. It answers questions about your data, runs quick analyses, exports results to Excel or CSV, and creates or updates records after a preview.
ARIA AI Reports
Describe the report you need in plain language, and ARIA builds the pivot report for you in TINA.
What the AI Assistant can do
- Find and analyze data: invoices, orders, imported orders, services, customers, suppliers and more, with results you can download as Excel or CSV.
- Partner records: create and update customers, companies, company offices, contact persons and suppliers. A passenger can be added starting from just an email address.
- Orders: process an imported service into a new or existing order, with passenger matching and a confirmation step.
- Client invoices: add, issue, void and reverse with a credit note, and record cashings.
- Supplier invoices: create invoices with rows, confirm, block or unblock them, and record payments.
The AI Assistant and the TINA MCP use the same TINA tools. For the full list with use cases, see What TINA AI can do.
How to turn them on
- Create your API key with your chosen provider: Claude or OpenAI.
- Open a ticket in the dcs plus support portal. The Customer Experience team confirms whether you add the key yourself in TINA's settings or dcs plus adds it for you, which models each feature uses, and the secure channel for anything you need to send.
- If you want separate cost tracking or rotation, assign a different key to each AI feature. TINA keeps keys in a list and never shows a stored key in full.
- Check your users' TINA rights. The AI Assistant acts as the signed-in user and can only see and do what that user can.
- Try your first prompts.
Never send a key in plain text
Do not email an API key or paste it into a ticket or a chat. Wait for the Customer Experience team to confirm the secure channel.
Level 2 · Turn on AI in TINA
Prepare TINA for the MCP
MCP (Model Context Protocol) is an open standard for connecting AI assistants to business systems. TINA includes an MCP server. Once it is active and added to Claude or ChatGPT, your users can look up, analyze and update TINA data from the AI app, each signing in with their own TINA account through OAuth 2.0.
This step is done once per TINA instance, by a TINA power user. dcs plus can do it for you on request: open a ticket in the support portal.
Check the requirements
- TINA version. TINA 4.0 or later, which includes the MCP server with OAuth 2.0.
- Internet access over HTTPS. Your TINA instance must be reachable from the public internet over HTTPS, with a valid certificate. Claude and ChatGPT connect from their providers' cloud, not from your users' computers, so an instance reachable only on a private network or VPN will not work.
- Firewall. If you restrict access to TINA, allow the IP ranges your AI provider publishes. See Help and references.
- Claude plan and role. A Claude organization on Team or Enterprise, and an Owner to add TINA. On Enterprise, a custom role with Manage access to Libraries also works.
- ChatGPT plan and role. A ChatGPT workspace on Business or Enterprise, and an Admin or Owner to create and publish the TINA app.
- TINA accounts. Every person who will use TINA from the AI app needs their own TINA account.
Activate the MCP endpoints in TINA
- In TINA, open Setup module → Configurations assistant, then the MCP configuration option.
- The page OAuth 2.0 and MCP autodiscovery (.well-known) configuration lists the endpoints TINA will activate, including the MCP server address and the OAuth 2.0 endpoints.
- Check that the .htaccess status reads "File exists and is writable", or that the file can be created. Then click Save.
- Copy the MCP server address from the top of the page. You need it in the next step.
File not writable?
Ask your system administrator to fix the permissions before you save. Saving changes only this instance's own rules in the .htaccess file, even if the file is shared.
Test instance
Each TINA instance has its own MCP server address. Repeat this step on your test instance and add it as a separate connector or app, for example "TINA test".
Level 2 · Turn on AI in TINA
Add the TINA MCP to Claude
A Claude Owner adds TINA once as a custom connector for the whole organization. Each user then connects with their own TINA account.
Add TINA as a custom connector (Owner)
- Open Organization settings → Connectors.
- Click Add, hover over Custom and select Web.
- Enter the name users will see, for example TINA.
- Paste the MCP server address you copied from TINA and click Continue.
- Review the authentication settings Claude detected and click Continue. TINA uses OAuth 2.0.
- Under Authentication, choose Sign in now or Sign in when needed. Do not choose No sign in.
- Under OAuth client, choose Register automatically. TINA registers Claude through its own registration endpoint.
- If you see a Request headers section, leave it empty. A token entered there would give every user the same access.
- Click Add.
Changing it later
After you add the connector, you can change its name or address, but not its authentication settings. To change those, remove the connector and add it again; users then connect again.
Connect as a user
- Open Customize → Connectors, find TINA (marked Custom) and click Connect.
- Sign in with your own TINA account on the TINA sign-in page.
- In a conversation, click +, open Connectors and turn TINA on.
Review before you approve
Claude can read and change data in TINA with your permissions. Review each tool request before you approve it, and choose Always allow only for tools you are comfortable letting Claude run without asking.
Level 2 · Turn on AI in TINA
Add the TINA MCP to ChatGPT
A ChatGPT Admin or Owner creates TINA once as a custom MCP app, tests it and publishes it for the workspace. Each user then connects with their own TINA account. App creation works on ChatGPT web only.
Apps, plugins, connectors
ChatGPT's interface is moving from Apps to Plugins, and OpenAI also uses the word connector. They mean the same thing here. Where your workspace still shows the older screens, both paths are given.
1. Allow custom MCP apps (Admin or Owner)
- Open Workspace settings → Permissions & Roles → Connected Data.
- Turn on Developer mode / Create custom MCP connectors. In newer workspaces, the permission is called Create plugins with MCPs.
- On Business, each admin or owner who will create the app turns developer mode on for their own account.
2. Create the TINA app
- Open Plugins, select +, then Add custom MCP server.
- Enter the name, for example TINA, and a short description, for example "Look up and update data in our TINA back office". ChatGPT reads the description to decide when to use the app.
- Under Connection, paste the MCP server address from TINA. Use the server URL option, not Tunnel.
- Under authentication, choose OAuth and keep the registration method ChatGPT detects. Do not enter a client ID or secret.
- Review the risk warning, select I understand and want to continue, and create the app. Sign in to TINA when asked and review the tools found.
Older Apps screens
Open Workspace settings → Apps → Create, enter the name, description and MCP server address, choose OAuth, select Scan Tools, sign in to TINA when prompted, wait for the scan, then select Create. The app is saved as a draft.
3. Test and publish
- Open a new chat, type @ and select TINA. Try a few questions and one harmless update.
- Publish: open the Admin console, select your workspace, open Plugins → Manage Legacy Apps → Drafts, and select Publish. On older screens, use Workspace settings → Apps → Drafts → Publish.
- On Enterprise, use Configure Access to choose which groups can use TINA, and Configure Actions to turn off actions you do not need.
After a TINA upgrade
ChatGPT keeps a snapshot of the TINA tools from when you published. After an upgrade that adds or changes tools, an admin refreshes the tool list in the workspace app settings. New actions stay off until you turn them on.
4. Connect as a user
- Open Settings → Plugins (or Apps on older screens), find TINA and click Connect.
- Sign in with your own TINA account.
- In a conversation, type @ and select TINA. Mention TINA again in follow-up questions that need fresh TINA data.
Level 3 · What TINA AI can do
What TINA AI can do
These are the TINA tools available to AI, grouped by area, each with a real-world use case and an example prompt. They are available through the TINA MCP in Claude and ChatGPT, and the AI Assistant inside TINA uses the same tools. Open a card to see the details.
How changes are protected
Every change follows the same pattern: validate or draft first, preview the result, then submit only after the user confirms. The AI acts as the signed-in user, so existing TINA roles and permissions still apply.
Finance
Client invoicingAdd, issue, void, reverse and cash invoices5 functionsCan change data
What it can do
- Add an invoiceFull invoicing for a reservation or partial invoicing for selected services
- Issue an invoiceValidates required data, then issues it
- Void an invoicePreview confirms it can be voided before anything changes
- Reverse with a credit notePreview shows whether reversal is allowed
- Add a cashing (payment)16 document types: receipt, bank transfer, credit card, cheque, deposit and more. One invoice at a time
Use case
Finance agent, month-end close
A supplier feed error created three duplicate invoices. The agent asks the assistant to void them and re-issue each one under the correct corporate account. The assistant previews every void, waits for the confirmation phrase, then re-adds and issues the replacements.
Why it matters: A multi-screen correction becomes a short conversation, with the same validation and an audit trail under the agent's own login.
Cashings are still one invoice at a time. There is no bulk or CSV import.
Supplier invoices and paymentsFull lifecycle from entry to payment5 functionsCan change data
What it can do
- Add a supplier invoice with rowsNew invoices only, created as not confirmed
- Confirm or unconfirmMoves the supplier balance up or down, with a consequence preview
- Block or unblockGenerates the accounting XML export
- Add a paymentPreview validates status and totals first
- Read rows and paymentsAnalytics and exports
Use case
Accounts payable clerk
An airline invoice arrives with 12 ticket rows. The clerk dictates the header and rows, reviews the preview with totals and validation results, submits, confirms, and later records the bank payment.
Why it matters: Entry, confirmation and payment in one thread, with the balance impact shown before each step.
To create a supplier invoice straight from a PDF, Word, TXT or XML file, see the use case Import supplier invoices into TINA.
Finance reference dataRates, VAT, banks and document series4 functionsRead only
What it can do
- Currency exchange and ratesConvert between currencies, list rates by date and type
- VAT and calculationsOffer and invoicing VAT percents, service calculations
- Banks, cities, countries, stationsReference lists
- Document series and templatesNumbering, currencies, users and templates
Use case
Accountant checking a foreign-currency invoice
A EUR invoice must be reported in RON. The assistant pulls the rate for the document date and converts the amount.
Why it matters: Correct rate, correct date, no spreadsheet lookup.
Records
Customers and passengersCreate, edit, block and unblock4 functionsCan change data
What it can do
- Create or edit a passengerDraft, patch fields, preview, submit
- Block a customerWith a blocking reason, after preview and confirmation
- Unblock a customerPreview then confirm
- Search and export customersAnalytics query and CSV/Excel export
Use case
Travel agent receiving a booking request
A new traveler writes in by email. The agent gives the assistant the details, the assistant opens a passenger draft, fills what it has, flags missing mandatory fields, and submits after a preview.
Why it matters: No blank form to fill, fewer typos, and the record exists before the call ends.
Corporates, offices and contactsCompany records and the people behind them5 functionsCan change data
What it can do
- Create or edit a corporateDraft workflow with preview before saving
- Create or edit a corporate officeBranches and billing entities
- Create or edit a contact personFor a corporate or a supplier
- Block or unblock a corporatePreview, reason, confirmation
- Read contracts, offices, trustsCorporate contracts, offices and holdings
Use case
Account manager onboarding a new corporate client
After signing, the account manager asks the assistant to create the company, add its Cluj office as a billing entity, and register two contact persons from the signed contract.
Why it matters: Onboarding takes minutes instead of three separate forms, and nothing is saved before the preview.
SuppliersAirlines, hotels, car rental and other vendors4 functionsCan change data
What it can do
- Create or edit a supplierDraft workflow with preview
- Block or unblock a supplierStops new transactions with that vendor
- Read contracts and productsSupplier contracts and supplier products
- Search and export suppliersAnalytics and CSV/Excel export
Use case
Procurement or back-office lead
A hotel chain is flagged for payment disputes. The assistant previews the block, shows what it affects, and blocks the supplier once confirmed, with the reason stored.
Why it matters: Fast, documented risk control without hunting for the right screen.
Operations
Orders and servicesReservations, services and imported bookings4 functionsCan change data
What it can do
- Create or edit an orderDraft workflow for new or existing orders
- Add or change a serviceOn an existing order or as the first service of a new one
- Process an imported serviceTurns a GDS or imported booking into an order service, with passenger mapping
- Read orders, offers and importsOrders, offers, imported services and documents
Use case
Ticketing agent with a queue of imported bookings
Imported air services land in TINA overnight. The agent asks the assistant to pick the first one, map the passengers to existing customers, attach it to the right order and save it.
Why it matters: Cuts the repetitive back-and-forth of order building and keeps imports from piling up.
Insight
Reporting and exportsAsk a question, get the numbers or a file4 functionsRead only
What it can do
- Query business dataInvoices, cashings, balances, orders, services, customers, suppliers, offers, contracts and more
- Export to CSV or ExcelInvoices, cashings, balances, supplier invoices and payments, customers, orders and others
- Profit and balancesGrouping of invoiced services and supplier rows to track margin
- Ticket lookupsBy ticket number across services and imported services
Use case
Sales or finance manager before a client call
Before a renewal meeting, the manager asks for the corporate's unpaid invoices and last quarter's volume, and exports the invoice list for the call.
Why it matters: The answer arrives in seconds, no report request to finance.
GDS transaction dataAmadeus, Sabre, Galileo, Apollo, Worldspan3 functionsRead only
What it can do
- Services and parsed filesOne analytics view per GDS
- Transaction detailsDrill into a single service transaction
- Sabre, Galileo, Apollo, WorldspanSame pair of tools for each system
Use case
Support agent investigating a ticket issue
A customer disputes a fare. The agent finds the service by ticket number and opens the raw GDS transaction to see exactly what was issued.
Why it matters: Faster root-cause answers without asking the GDS team.
Administration
Users and accessApplication users and login control4 functionsCan change data
What it can do
- Create or edit a userPassword and access rights are not set through the assistant
- Block a user loginUntil a given date and time, after preview
- Unblock a loginClears an active block
- Read users, offices, departmentsDirectory data and exports
Use case
IT administrator handling a departure
An employee leaves on Friday. The administrator asks the assistant to block the login until a far-future date, effective immediately.
Why it matters: Instant offboarding with a recorded action, without touching access rights.
Calendar eventsPlan and track follow-ups2 functionsCan change data
What it can do
- Create or edit an eventDraft workflow with preview
- Read and export eventsAnalytics and CSV/Excel export
Use case
Account manager after a client call
The call ends with a follow-up promised in two weeks. The assistant creates the calendar event tied to the context discussed.
Why it matters: Follow-ups logged in TINA while the conversation is still fresh.
Level 4 · Use cases
Import supplier invoices into TINA
How an agency turns the supplier invoices it receives by email into TINA supplier invoices: Claude reads each document, TINA validates it through the TINA MCP, and a person confirms before anything is saved.
- Who: accounts payable, finance and back-office teams
- You need: the TINA MCP in Claude, TINA rights to add supplier invoices and suppliers, and the skill in Downloads
The problem
Every day, agencies receive supplier invoices as PDF attachments from dozens of suppliers: hotels, tour operators, transport companies. Each one has its own layout, its own labels and its own date and amount formats.
Every invoice has to be entered in TINA as a supplier invoice. Done by hand, that means retyping each field and making mistakes in the series, the VAT rate or the due date.
What was tried before
Agencies hired outside providers to read the files with OCR and send the data to TINA through the API. The results were poor, for three reasons:
- every new supplier or changed layout needed a new template;
- errors showed up only after the data had reached TINA;
- nobody asked a person when a row was ambiguous, for example a commission under the margin scheme or a deducted advance.
How varied the documents really are
We worked on a real sample: 40 PDF files, which turned out to be 31 unique invoices from domestic suppliers (hotels, tour operators, transport). Some invoices arrived in two layouts: the e-Factura rendering and the issuer's own PDF.
The files fell into six families:
| Family | What it looks like |
|---|---|
| 1. e-Factura rendering | Fixed labels, VAT shown by rate |
| 2. Classic Romanian invoice | Series and number, supplier and buyer blocks |
| 3. Hotel folio from the property system | Daily lines, payments, VAT summary at the end |
| 4. Tour operator invoice, margin scheme or SDD | A negative "commission ceded" line, no VAT printed |
| 5. Advance invoice, and final invoice with the advance reversed | One of them totals 0.00 |
| 6. Not an invoice | Annexes, transport reports, proformas. Not imported |
And the variations inside them:
- dates in at least six formats (DD.MM.YYYY, DD-MON-YY, "15 Aug 2026" and others);
- amounts written as "1.234,56" and as "1,234.56", sometimes within the same family;
- series and number printed together ("TPVB214829") or separately;
- invoices with no due date, with "payment in 15 days", or with instalments;
- 11%, 21% and 0% VAT on the same invoice (food at 11%, drinks at 21%);
- city tax, tips and parking;
- one-cent differences between the VAT rows and the printed total;
- EUR invoices with a RON equivalent at the central bank rate plus a margin;
- suppliers who are private individuals;
- buyers other than the agency doing the import.
The approach: Claude reads, TINA validates, a person confirms
- Claude reads each document the way an accountant would, whatever the layout, with no template per supplier.
- TINA validates through the TINA MCP, which exposes more than 150 tools. For supplier invoices the flow has four steps: open a draft; preview it, which is where TINA runs its real validation; submit, only after confirmation; then confirm, block or pay the invoice, each as a separate decision.
- A person confirms. Nothing enters TINA without a full preview and without the user typing exactly CONFIRM.
How the rules were built, in conversation
The rules came out of a conversation with Claude over the sample, one round at a time. These example prompts are representative of that conversation; they are not a transcript.
- "Here are 40 supplier invoice PDFs we received last month. Read them, group them by layout, and tell me which files are not invoices or are the same invoice twice."
- "For each invoice, map the data to TINA's supplier invoice fields. Show me a table with the field, the value, where on the document you found it, and a status: Found, Derived or Missing."
- "Always split the invoice number: the letters at the start are the series, the digits are the number. Keep leading zeros."
- "If an invoice has no due date, use the invoice date plus 7 days and tell me which invoices got it. If a payment term is printed, calculate from it."
- "Map the rows to service codes: accommodation, breakfast, food and drinks go to hotel; parking and tips to other services; city tax to hotel as a tax row; transfers to transfer; flights to ticketing."
- "Never change the net or VAT values printed on the invoice. If the VAT rate isn't printed, derive it from VAT divided by net and use the nearest rate configured in TINA."
- "Look up each supplier in TINA by fiscal code, then by name. If it doesn't exist, create it from the invoice, with its bank account if the bank exists in TINA."
- "Preview every invoice in TINA and show me every warning. I'll confirm the whole batch once."
- "Now turn everything we decided into a reusable skill that any agency can adapt."
What these rounds taught us:
- Only TINA's preview runs the real validation. That is how we found that the 11% and 21% VAT rates were not configured for some service codes.
- VAT rates are configured per service code, and the commission code accepts only 0%.
- Invoices cannot be edited through the MCP once created, so everything must be right before submitting.
- TINA's bank list is short, and missing banks cannot be added through the MCP.
The skill: the rules, written once
A skill is a set of instructions that Claude uses automatically when a user attaches an invoice and asks to import it. Your agency adapts it once to its own TINA configuration.
What the skill contains
- A setup checklist
- The 10-step workflow
- The TINA fields
- Date and amount formats
- The six document families
- Row mapping rules and the service code table
- Suppliers: lookup, creation, bank account
- Checks before the draft
- VAT rates
- What the user is shown
- Safety rules
What your agency adapts
- The MCP connection and user rights
- VAT rates on the service codes you use
- The service code table
- Banks
- The rule for a missing due date
- A first run on a test environment
- A check against your DPA and internal AI policy
Once the skill is in place, the user attaches the invoice and writes:
For a batch, attach all the files and write:
Using ChatGPT
The skill is written for Claude, and the import was tested with Claude. In ChatGPT, give the same rules to the assistant at the start of the conversation.
The result
- All 31 invoices in the sample were created in TINA, and 26 suppliers were created straight from the invoices. With the demo invoices added afterwards, the total reached 33 invoices and 28 suppliers.
- No net or VAT value was changed.
- Every invoice was created as not confirmed. Confirming it remains a separate decision, taken in TINA.
- The demo invoice in the video is OHS 0002316 from The Oakridge Hotel, a fictitious supplier: 6 rows across three VAT rates, EUR 869.48 in total. The supplier was created from the invoice with its bank account linked, and the preview passed with no warnings.
Safety and control
- Every invoice goes through TINA's preview, and submitting requires the exact phrase CONFIRM.
- No personal data, such as guest names or personal identification numbers, is copied into descriptions or comments.
- Run the first imports on a test environment: documents created through the MCP cannot be deleted through it.
Downloads
- MP4Video: Supplier Invoices into TINAMP4, about 1:53 · 15.7 MB
- ZIPThe supplier invoice import skillReady to upload to Claude. Unzip it to read the rules, and adapt section 0 and the service code table to your TINA configuration before use · 4 KB
- PDFDemo invoice from the videoTry the import yourself, on a test environment · 59 KB
Level 5 · Run it like a pro
Tips for great results
TINA AI works best when you ask the way you would brief a colleague. A few habits make a big difference.
Be specific
Use the identifiers you have: invoice numbers, order numbers, ticket numbers, corporate names, dates. "Invoice 20458" beats "the invoice from last week".
One task at a time
Ask for one change per message, especially when it saves data. For several records, ask for a list first, check it, then confirm it once.
Read the preview
The preview is your control point. Check amounts, dates, the partner and the currency before you confirm.
Ask for files
Ask for results "as Excel" or "as CSV" when you want to share or keep them.
More example prompts
Good habits
- Practice on a test instance. Saving creates real records, so train new users on a TINA test instance first.
- Keep TINA off when you do not need it. In Claude or ChatGPT, turn TINA on only in conversations that need it.
- Start a new conversation for a new topic. Long conversations mixing several tasks lead to mistakes.
- If something looks wrong, stop. Do not confirm. Ask the AI to explain, or cancel and start again.
Level 5 · Run it like a pro
Security and data protection
TINA AI acts in TINA as the signed-in user. Treat it with the same care as that user's TINA account, and your AI accounts and keys like any other business system.
Accounts and access
- Keep at least two owners in your Claude organization or ChatGPT workspace, using company-controlled accounts.
- Give owner and admin roles to as few people as possible, and review them quarterly.
- Use single sign-on where you can, so leaving the company also ends access to the AI app.
- Give each user only the TINA rights they need. The AI can do anything the signed-in user can do in TINA.
- When someone leaves, remove their AI seat and block their TINA user. Blocking the TINA user also ends their access to the TINA MCP.
API keys
- Store keys in a password manager or secrets vault, never in spreadsheets, documents, emails, tickets or chats.
- Use service account keys, never a person's key, and limit who can see them.
- Rotate keys on a schedule, and immediately when someone with access leaves.
- If a key is exposed, revoke it with the provider first, then create a replacement and update TINA.
- Keep spend limits and alerts in place on every key.
TINA MCP
- Review every request to create, change or delete data before you approve it.
- Block or turn off the TINA tools and actions you do not need.
- If your firewall restricts TINA, allow your AI provider's published IP ranges instead of opening TINA to all internet traffic. Check the list regularly.
- If the AI does something you did not expect, turn TINA off in the AI app, then open a ticket in the support portal.
Data protection (GDPR)
When a user asks a question, TINA sends the AI provider only the data that request needs, for example a customer record or the rows of a report. That data can include personal data about travelers and contacts.
The connection runs directly between your AI provider and your TINA instance. dcs plus is not part of it and does not see your conversations. Your AI provider processes the data under your organization's agreement with them, including their data processing addendum. Add the provider to your record of processing activities, as you would any other processor.
Level 5 · Run it like a pro
Troubleshooting
Most problems come from network access, a step that was not saved, or a limit that was reached.
The AI app cannot reach TINA when you add the connector or app
Check the MCP server address you pasted, that TINA is reachable over HTTPS from the internet, and that your firewall allows your AI provider's published IP ranges.
The TINA sign-in fails
Check that the MCP configuration in TINA was saved and that the .htaccess status showed no error. Then remove the connector or app and add it again.
Users cannot find TINA in Claude
Check that an Owner added the connector in Organization settings, that the user clicked Connect, and that TINA is turned on in the conversation.
New TINA tools do not appear in Claude after an upgrade
Start a new conversation. If the tools are still missing, ask the user to disconnect and connect TINA again.
Users cannot find TINA in ChatGPT
Check that the app was published, not only saved as a draft, that the user belongs to a group with access (Enterprise), and that the user clicked Connect.
You cannot see the option to add a custom MCP server in ChatGPT
Check that custom MCP apps are allowed in Workspace settings and, on Business, that developer mode is on for your own account.
New TINA tools do not appear in ChatGPT after an upgrade
Refresh the tool list from the workspace app settings, then turn the new actions on.
The AI cannot see some data or cannot complete an action
The user's TINA rights limit what the AI can do. Ask your TINA administrator to check them.
The AI Assistant or ARIA AI Reports stopped working
Check the API key with your provider: it may have expired, run out of credit, or reached its spend limit. Everything else in TINA keeps working while the AI features are stopped.
Users have to sign in to TINA again often
Open a ticket in the support portal, so dcs plus can check the session settings for your TINA version.
Level 5 · Run it like a pro
Frequently asked questions
Who pays for the AI?
You do, directly to your AI provider: per seat for the Claude organization or ChatGPT workspace, and per use for API keys. dcs plus does not charge you for AI usage and does not add a margin. Charges for TINA itself follow your dcs plus contract.
Do we need both an organization and an API key?
Only if you want both kinds of features. The API key powers the AI Assistant and ARIA AI Reports inside TINA. The organization lets your staff use TINA from Claude or ChatGPT through the TINA MCP. See What you need.
Is a Claude or ChatGPT seat the same as a TINA user?
No. Each person who uses TINA from Claude or ChatGPT needs both a seat in the AI app and their own TINA account.
Does the AI see all our TINA data?
No. It sees only what the signed-in user can access in TINA, and only the data a request needs.
Can the AI change data in TINA?
Yes, if the user's TINA rights allow it. It always prepares a draft, shows a preview, and saves only after the user confirms.
Is our data used to train AI models?
Not by default. Anthropic and OpenAI do not use data from their business plans or their APIs to train their models, unless a user sends feedback, for example with the thumbs up or down buttons.
Can we keep our data inside the EU?
With OpenAI, yes: ChatGPT Enterprise workspaces and eligible API projects can store data in Europe, chosen when they are created. With Anthropic, an EU-only option is not available directly. Review the options with your data protection officer before you start.
What happens if an API key hits its limit or runs out of credit?
The AI features that use that key stop until you raise the limit, top up credit, or the month resets. Everything else in TINA keeps running.
Is our account or key shared with other customers?
No. Your organization, workspace and keys belong to your company only. dcs plus never reuses one customer's key for another.
Do we need a separate connector for a test instance?
Yes. Each TINA instance has its own MCP server address. Add the test instance as a second connector or app with a clear name, for example "TINA test".
Can we use another AI client, such as Microsoft Copilot?
The TINA MCP follows the open MCP standard and uses OAuth 2.0, but this guide covers Claude and ChatGPT. Open a ticket before you set up another client, so dcs plus can confirm what your TINA version supports.
Level 5 · Run it like a pro
Help and references
Questions about any of this?
Open a ticket in the dcs plus support portal at support.dcsplus.net, or reach out to your dcs plus contact. The Customer Experience team picks up tickets from there. Do not include passwords, keys or tokens in a ticket.
Anthropic (Claude)
- Get started with the Team plan
- Roles and permissions
- Set up single sign-on
- Custom connectors using remote MCP
- Get a Claude API key
- Workspaces in the Claude Console
- Anthropic IP addresses
- Is my data used for training?
- Anthropic Data Processing Addendum
OpenAI (ChatGPT)
- Sign up for ChatGPT Business
- Managing members, seat types and roles
- Setting up SSO for ChatGPT Business
- Developer mode and MCP apps in ChatGPT
- Managing projects in the API Platform
- API keys and service accounts
- IP egress ranges for ChatGPT connectors
- Data residency for ChatGPT
- Business data privacy, security and compliance