First steps

In under ten minutes you can activate your account, invite your team and put Amadeus and your departmental agents to work. This guide takes you from sign-up to your first task, step by step, with nothing technical in between.

Shara is an AI employee team for your company. Instead of configuring technical flows, you talk to Amadeus (the orchestrator) in natural language, and it coordinates the specialized departmental agents: Patterson (Sales), Hopkins (Marketing), Graham (Finance), Holmes (Legal), Maslow (HR), Deming (Operations), Eastman (Product), Rockefeller (Strategy), Turing (IT) and Wanamaker (Customer service), among others. In total there are 21 agents: Amadeus plus 20 specialists. Data handling and compliance are designed for the EU (GDPR).

Before you start: what you’ll need

You don’t need to install anything technical or know how to code. Have four things ready and the start will be smooth:

• The activation key you received by email when you signed up (format SHARA-XXXX-XXXX-XXXX-XXXX).
• The plan you’ll be using (First, Pro, Max or Concerto Local); you can change it later.
• An authenticator app on your phone (Google Authenticator, Authy, 1Password or similar) for two-factor verification. It’s optional, but whoever administers the company needs it to invite their team.
• Knowing which tool you want to connect first (usually email or your CRM) and having access to that account.

Get started in 5 steps

1. Install the app and activate your account. Download the desktop app (Windows, macOS or Linux), open it and, on the sign-in screen, click Activate with company key. The activation key is redeemed in the app, not on the web: paste it, check the company and plan it shows, and enter your name and a password. Then a wizard walks you through your company, your team, your goals, your tone and your agents. When you’re done, your workspace will be ready with Amadeus and the agents your plan lets you choose. Also turn on two-factor authentication (2FA): it’s optional, but you need it to invite your team.
2. Invite your team by role. From Team → Add employee, assign a role and one or more departments to each person (for example, management, finance or customer service). The role determines which agents and actions each member can access; not everyone needs to touch everything.
3. Talk to Amadeus in natural language. Open the chat and describe what you need the way you’d tell an employee. Amadeus decides which departmental agent gets involved and gives you a plan before executing anything. Example: “Amadeus, give me a summary of this week’s 5 hottest sales opportunities and draft a follow-up email for each.”
4. Connect a tool. In Integrations, link your Gmail, your CRM or another source via OAuth. Connectors are available in every plan starting from First (HubSpot, Pipedrive and Salesforce from Pro). With Gmail connected, Patterson can read and draft emails; with your CRM, sync contacts and opportunities.
5. Leave your first task. Ask Amadeus for a one-off task that runs in the background (“review this month’s invoices and leave me a summary of the ones that don’t add up”). Agents work while you carry on with your day and let you know when they’re done. Scheduled tasks that repeat on their own are not available yet: for now, you ask for each task when you need it.

No action with a real-world impact (sending emails, moving money, changing records) runs without your sign-off. Every plan goes through explicit approvals and spending limits. They are set in STU (the unit that measures consumption, explained below) and by default stop at 1M STU per run, 10M per hour and 80M per day. The owner or an admin can edit or turn them off. If something spikes, Shara stops itself.

Step 1: install the app, activate your account and set up your company

Activation comes first and only happens once. Whoever activates the account becomes the owner of the company within Shara:

1. Install the desktop app (Windows, macOS or Linux) and open it. On the sign-in screen, click Activate with company key.
2. Paste your key SHARA-XXXX-XXXX-XXXX-XXXX: the key is redeemed in the app, not on the web. The app shows the company and plan it belongs to. Enter your name and a password of at least 10 characters and click Activate account.
3. Follow the setup wizard, which opens by itself: your company details (trade name, sector and team size), your key team, your goals for the quarter, your company’s tone and your starting agents. You can skip it and set everything up later from Settings.

Afterwards, in Settings → Business hours you set your schedule and timezone: outside it, agents switch to automatic saving mode.

Two-factor authentication (2FA) is optional, but it’s worth turning on on day one: in My account → Two-factor authentication you scan the QR code with your authenticator app, enter the 6-digit code and save the recovery codes shown on screen somewhere safe, because they’re your way in if you lose your phone. If you are the owner or an administrator, you need it to invite your team, create API keys, edit an agent’s identity or change your password. For everyone else, you decide: in Settings → Security you can require it from the whole team.

When you’re done, you land in the app with Amadeus waiting and your agent team already available. There are no servers to configure: the desktop app is where you work day to day, with the Amadeus chat, native notifications and the approval inbox at hand.

Step 2: invite your team by role

Each person comes in with a role, and the role defines what they can see and do. The idea is simple: the owner and the admins can talk to Amadeus (who coordinates every department); everyone else talks to the agent for their area. That way whoever runs finance doesn’t touch sales, and vice versa.

Role	What it can do
Owner (the app labels it “CEO”)	Owner of the company. Full access. It can’t be assigned or removed from the team screen.
Admin	Runs the company: team, billing, audit and all agents. Can use Amadeus.
Director	Leads a department: manages their team and their agent, and sees that department’s work.
IT (admin_it)	Handles the technical side: integrations, keys and system health. Doesn’t touch team or billing.
Operator	Works with their department’s agents and sees their own work.
Viewer	Read-only: sees their own work and changes nothing.

To invite someone: in Team, click Add employee and fill in the email, the name, the departments (more than one is fine), the working schedule and the role. The person receives a link that lets them create their account: the email is already filled in and can’t be changed, they enter their name and a password, and two-factor authentication is optional unless the company requires it. They join with exactly the permissions you assigned; if their role isn’t an administration one, they work from the desktop app, and the invitation page itself gives them the downloads. You can change someone’s role or revoke their access at any time; in Settings → Members you only see the members and edit the roles.

Inviting is a sensitive operation: if you are the owner or an administrator, you need two-factor authentication turned on (My account → Two-factor authentication) before sending your first invitation.

Start with few roles and open them up as needed. It’s easier to grant more permission than to take it away, and the read-only role is perfect for someone to see how the team works before letting them execute actions.

Step 3: your first chat with Amadeus

Open the chat and write to Amadeus the way you’d talk to an operations director. There are no commands or syntax: describe the intent and the result you want. Amadeus interprets it, decides which departmental agent gets involved and, before touching anything, gives you back a plan of what it intends to do.

For your first time, ask for something read-only, with no actions that go out into the world. For example: “Amadeus, give me an executive summary of the last week with the most important thing from each area.” You’ll see how it delegates, consolidates the response from several agents and delivers it to you in a single message with your tone.

Always review the plan before approving: that’s where you see which agent acts, which tools it will touch and what actions it proposes. Approving is one click; rejecting or editing, too.

Step 4: connect a tool via OAuth

Connectors are what turns your agents from “advisors who talk” into “employees who do.” With email connected they can read and draft messages; with your CRM, query and update opportunities. The process is the standard OAuth flow you already use to sign into any app with your Google or Microsoft account:

1. Go to Integrations and choose the service (Gmail, Google Calendar, Outlook, Slack and Holded on any plan; HubSpot, Pipedrive and Salesforce from Pro; among others).
2. Click Connect. The provider’s own login screen opens: you authorize there, not in Shara. Shara never sees your password.
3. Grant only the permissions you need. If the agent will only read, don’t give it write permission (you can request a subset of the default permissions).
4. When you return, the integration shows as connected and the agent that needs it uses it automatically.

Reading from your tools is direct; writing requires your approval. In other words: an agent can read your inbox to summarize, but sending an email always goes through your sign-off. You have the full detail (catalog, permissions and security) in Connectors.

Step 5: leave your first task

With a tool connected, you can already delegate real work. It is requested in natural language, as a one-off task: an assignment Amadeus resolves right away and lets you know when it’s done. Example: “Review the new leads in the CRM and draft me a contact email for each one.”

# One-off background task
Amadeus, review this month's invoices, flag the ones that don't match up
and leave me a summary of what needs reviewing.

Scheduled tasks that repeat on their own are not available yet: for now, you ask for each task when you need it.

Agents work while you carry on with your day. When they finish, they let you know; and if along the way an action that goes out into the world comes up (an email, a payment, a change to a record), they don’t execute it: they leave it as a proposal in your approval inbox for you to decide.

What to ask Amadeus

There’s no syntax to learn: write the way you’d talk to a colleague. Amadeus interprets the intent, chooses the right agent and proposes a plan. The more specific you are about the result you want, the better. A few examples to get started:

# Sales (Patterson)
Amadeus, review the new leads in the CRM and draft a first contact email for each one.

# Finance (Graham)
Amadeus, give me this month's expense summary and flag any unreconciled invoices.

# Customer service (Wanamaker)
Amadeus, summarize today's support tickets and propose a reply for the 3 most urgent ones.

# Strategy (Rockefeller)
Amadeus, compare our revenue this quarter against last quarter and point out what changed.

And a few more for the rest of the areas, so you see how far the team reaches:

# Marketing (Hopkins)
Amadeus, prepare three LinkedIn post ideas for this week in our tone.

# HR (Maslow)
Amadeus, put together the onboarding script for Monday's new hire.

# Operations (Deming)
Amadeus, check the status of open orders and let me know which ones are running late.

# Analytics (Nightingale, additional agent)
Amadeus, turn this quarter's sales data into a short report with conclusions.

A good request usually has three things: what you want, where the data comes from and what format you expect. “Summarize the tickets (what) from the helpdesk (where) in five lines and propose a reply to the three most urgent (format)” performs better than a simple “look at the tickets.”

How to choose your plan

Consumption is measured in STU (Shara Token Units), the billable unit of work for the agents. Each plan includes a monthly STU bundle; if you go over it, the overage is charged at €5 per million STU. You can grow your team with an additional agent for €99/month, which adds 15M STU to your bundle. With six-month billing you’re billed for five months out of six and with annual for nine out of twelve, both with a commitment for that period.

Plan	Price	STU included	Ideal for
First	€129/month	50M STU	Getting started and validating use
Pro	€349/month	140M STU	Teams up and running
Max	€690/month	280M STU	Intensive use
Concerto Local	Contact sales	60M STU in the cloud (optional)	Data on your own servers

To choose without overthinking it, these signals are usually enough:

• If you’re still testing how Shara fits into your day-to-day, start with First. It’s the plan for validating use without committing to much.
• If the team will already use it daily and you want director Amadeus distributing work across several departments, Pro is the sweet spot for most SMEs.
• If volume is high and you want Amadeus at maximum capacity for complex tasks, go to Max.
• If, due to regulation or internal policy, data can’t leave your servers, your plan is Concerto Local (it runs on your own infrastructure, with an optional 60M STU cloud bundle that you switch on or off).

Don’t obsess over getting it right the first time: you can change plans whenever you want, and the STU overage acts as a buffer if you go a little over in a given month. You have the detail in STU and quotas.

Amadeus is included in every plan. The AI models behind the agents are identified only by their alias: Symphony (maximum capacity, from Max), Sonata (balanced), Prelude (agile and fast) and Concerto (local execution, on your own infrastructure, in Concerto Local). In the app, Shara picks the model for each step according to your plan, the time of day and your quota; you don’t have to choose it.

How your team learns with use

Each agent has its own IDENTITY.md file: its instructions, tone, policies and business knowledge. It isn’t rewritten all at once; instead it evolves through versioned patches (each adjustment is logged) so you can fine-tune behavior safely and revert if needed.

Besides the IDENTITY.md, your team has memory: it retains context about your company (what your products are called, who your key clients are, how you write your emails) and reuses it in later conversations. The more you use it, the more it adapts to your way of working, always within your organization and without mixing data with other clients.

• Start with a single real task (an email, a summary) to see the approval flow end to end.
• Always review the plan Amadeus proposes before approving: that’s where you see which agent acts and which tools it will touch.
• Adjust an agent’s IDENTITY.md whenever you want to change its tone or its rules; changes apply as patches.
• Correct it on the spot: if a draft doesn’t convince you, tell it what you’d change. That correction feeds how it will work next time.
• The spending limits come already set and don’t penalize normal use: if one trips, something has run away and it’s worth a look.

Your first 30 minutes

If you want a concrete plan for the first half hour, this walkthrough leaves you with Shara already working and the feeling of having seen the full cycle:

1. Minutes 0-5: install the app, activate your account with your key and go through the wizard. Turn on 2FA too and save the recovery codes.
2. Minutes 5-10: invite one key person with their role. One is enough to test with.
3. Minutes 10-15: talk to Amadeus with a read-only request and read the plan it gives you back.
4. Minutes 15-22: connect your email or your CRM via OAuth, granting only the exact permissions needed.
5. Minutes 22-30: ask for a real task that generates an action (an email draft), review it in the approval inbox and approve or edit it. There you’ve seen the full cycle: request, plan, execution, approval, result.

Common beginner mistakes

Almost all the early stumbles are the same ones. If you know them in advance, you’ll avoid them:

• Granting too many permissions when connecting. You don’t need write permission if the agent will only read. Start in read mode and expand when you need to.
• Approving without reading the plan. The plan is your chance to correct before anything executes. Read it, especially the first few times.
• Asking for vague things. “Help me with sales” gives a generic result. Be specific about the what, the where and the format.
• Inviting everyone as admin. Only the owner and a few admins need to talk to Amadeus and approve. Everyone else works better with their area role.
• Losing the 2FA recovery codes. Save them when you activate them; they’re your way in if you change phones.
• Ignoring a spending limit that has tripped. Normal use doesn’t trigger them: if one fires, there is something to review in the request or in an integration.
• Waiting for it to be “perfect” before using it. The team learns with use: the sooner you give it real tasks, the sooner it adapts to your way of working.

Questions while getting started? Write to support@aiginer.com.

Ready for the next step? Explore the full agent catalog, learn to connect more tools or dig into how consumption is measured from the rest of the documentation.