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 automation, 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: Carnegie (Sales), Kotler (Marketing), Graham (Finance), Holmes (Legal), Maslow (HR), Deming (Operations), Rosling (Analytics), Porter (Strategy), Turing (IT) and Carlzon (Customer service), among others. In total there are 21 agents: Amadeus plus 20 specialists. Data handling and compliance are designed for the EU (GDPR).

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.
• Knowing which tool you want to connect first (usually email or your CRM) and having access to that account.

1. Activate your account. Enter your activation key in the panel, confirm the plan (First, Pro, Max or Concerto Local) and set up two-factor authentication (2FA). When you’re done, your workspace will be ready with Amadeus and the available agents.
2. Invite your team by role. From Settings → Team, send invitations assigning a role 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. With Gmail connected, Carnegie can read and draft emails; with your CRM, sync contacts and opportunities.
5. Create your first automation or leave a task. Ask Amadeus for a recurring task (“every Monday at 9:00, send me the cash flow status”) or a one-off task that runs in the background. Agents work while you carry on with your day and let you know when they’re done.

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 kill-switches: a maximum of €5 per run, €50 per hour and €400 per day. If something spikes, Shara stops itself.

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

1. Go to the Shara panel, choose Activate account and paste your key SHARA-XXXX-XXXX-XXXX-XXXX.
2. Confirm the plan (the one you already have will appear marked) and fill in your company’s details: trade name, sector, team size and business hours. That schedule matters: outside of it, agents switch to automatic saving mode.
3. Verify the administrator’s email and set your timezone (Europe/Madrid by default).
4. Turn on two-factor authentication (2FA): scan the QR code with your authenticator app and enter the 6-digit code. Save the recovery codes shown on screen somewhere safe; they’re your way in if you lose your phone.

When you’re done, you land in the panel with Amadeus waiting and your agent team already available. There are no servers to configure or anything mandatory to install, though the desktop app is the recommended way to work day to day (native notifications and the approval inbox at hand).

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

To invite someone: Settings → Team → Invite, enter the email, choose a role and departments, and send. The person receives a link, signs in with their account (with Google, for example) and joins with exactly the permissions you assigned. You can change someone’s role or revoke their access at any time from the same screen.

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.

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.

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, HubSpot, Pipedrive, Holded, 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.

With a tool connected, you can already delegate real work. There are two ways to do it, and both are requested in natural language:

• 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.”
• Recurring automation. A task that repeats over time. Example: “Every Monday at 9:00, send me the cash flow status and let me know if there are overdue invoices.”

# Recurring automation
Amadeus, every Friday at 17:00 summarize this week's support tickets
and prepare a follow-up email for the 3 clients with the most incidents.

# 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.

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.

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 (Carnegie)
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 (Carlzon)
Amadeus, summarize today's support tickets and propose a reply for the 3 most urgent ones.

# Strategy (Porter)
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 (Kotler)
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 (Rosling)
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.”

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 annual billing there’s a 10% discount.

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 (on-premise, no cloud component).

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.

The AI models behind the agents are identified only by their alias, based on the demands of each task: Symphony (maximum capacity), Sonata (balanced), Prelude (agile and fast) and Concerto (local execution, on your own infrastructure, in the Local Plan). Amadeus assigns the right model to each step automatically; you don’t have to choose it.

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.
• Keep the kill-switches active: they’re your spending safety net and don’t penalize normal use.

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: activate your account, confirm the plan and set up 2FA. 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.

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 management. Only the owner needs 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.
• Turning off the kill-switches “so they don’t get in the way.” They don’t get in the way of normal use and they’re your spending safety net. Leave them on.
• 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.

Self-serve on First and Pro; guided onboarding on Max and Concerto Local. 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.