Getting started with ALMAS

Slide 1 — Welcome to ALMAS

• ALMAS is an AI business management platform for startups and small teams: one app, many isolated company workspaces.
• You'll learn: the shell, the modules you'll touch daily, sharing, and how to get help.
• Today's deck is ~45 minutes; refer back to the User Manual for depth.

Slide 2 — What's a tenant?

• A tenant = an isolated workspace with its own users, data, and settings.
• You can belong to many tenants (e.g. employer + personal + side project).
• Switch with the dropdown in the top bar, or T 1–T 6 for the six pinned slots.

Slide 3 — Tour of the shell

• Sidebar (left): the ALMAS pentagon mark at the top (it changes color to match the active module — green for Accounting, coral for Legal, violet for Sales, etc.), then every module grouped by area.
• Top bar: global search, AI file drop, notifications bell, tenant switcher, profile menu. The browser tab favicon also changes to match the current module.
• Main area: where each module lives. Same layout pattern across all modules.

Slide 4 — Common page patterns

• List page: title + Create button + filters + refresh + a list/grid of records.
• Create / Edit: opens in a modal. Required fields marked. ESC to dismiss.
• View: breadcrumb + status badge + tabs for related data.
• Breadcrumbs remember your path: open a task from inside a project → breadcrumb shows Projects > Project ABC > Task XYZ. Click any earlier crumb to return there. Same task opened from the global tasks list (or a notification) shows the simpler Tasks > Task XYZ form.
• Buttons you can't use are hidden or greyed out (permission-gated).
• Don't want to memorize any of this? Open Help center → Guided tours and pick a tour — ALMAS navigates the real pages and spotlights where to click, step by step (first project, clients, invoicing, expenses, contracts). Finished tours get a Completed badge.
• Or just ask the Ghost (plans with the AI Agent): the floating ghost button, bottom-right on every page. Tell it what you want to do — it answers live, looks up your data, and can start the right guided tour for you.
• The Ghost can also do things for you — always with your OK first: ask it to create a task or record an expense and it shows a confirmation card; nothing happens until you press Confirm. Your permissions apply, every action is recorded, and a daily AI allowance protects your workspace's budget.
• Ask for it "on screen" and the Ghost drives the app for you: it opens the page, brings up the form, and types the values while you watch — Pause, Take over, or Stop from the control bar anytime. You always click Save: the Ghost stops at the button and waits for you; Cancel the form and nothing is kept. Great for learning where things live.
• Your first completed tour or drive earns the Onboarding achievement (50 points).
• Tours and the Ghost speak your language — switch to Português/Español in your avatar menu and the tours, buttons and the Ghost's answers follow. New users get a "New here? Take the tour" compass chip for two weeks — click starts the tour, snooze dismisses it.
• See your history under profile menu → My timeline: every tour and drive you ran, as plain sentences, newest first.
• Floating reminders (bottom-right, above the ghost): a rocket = open Getting-started items; clock / alarm / red warning = bills due soon / today / overdue, with the count. Click to go there; ⋯ to snooze (4h, tomorrow, a week, mute) — the grey bell chip holds snoozed ones so you can re-enable them.
• Hide all floating buttons for a while: the eye-slash button on top of the column → 4 hours / 1 day / 1 week. The reminders, the ghost and the theme gear disappear on every device and come back on their own; avatar menu → Show floating buttons (or My profile → Preferences → Floating buttons) brings them back now.
• Getting started checklist (profile menu → Help): first project, first task, first invoice, first bill… ticks itself off when you do the real thing, shows only what your role can do, and each item has a shortcut — Go there / Show me / Ask the Ghost. ✕ dismisses what you already know.
• Achievements & medals (profile menu → Progress & rewards → Achievements, or My profile → Achievements / Inventory): concluding tasks, paying bills, logging in day after day and finishing the checklist earn XP and unlock achievements with a collectible — Press Start, Taskinator 2000, Show Me the Money, Dial-Up Devotee, Y2K Survivor… A toast tells you the moment one unlocks; your level (Freshman → God) sits on your avatar. Medals live in the workspace they were earned in and are worth more on higher plans.
• Leaderboard (profile menu → Progress & rewards): your workspace's monthly race by XP earned here — top three get Employee of the Month / High Score / Honorable Mention when the month closes; last month's podium stays on the page. Your global standing (leaderboard page + My profile → Achievements) shows only your position among all ALMAS users this week / month / year — there is no global list. Hide me from leaderboards (My profile → Achievements) keeps you earning but off every board.
• Quests (profile menu → Progress & rewards): today's three (sign in · conclude a task · interact once) and this week's four (3 tasks · create a task · pay 2 bills · 5 interactions) tick themselves off as you work; clear a whole day for Blockbuster Night, a whole week for Tamagotchi Keeper, five sweep days in one week for Perfect Attendance '99. The floating Today's quests reminder shows what's still open and vanishes once the day is swept. A task you created yourself never scores — someone else has to create or assign it.
• Rewards (profile menu → Progress & rewards): redeem earned items for real perks (coffee → gift card); requests wait in a fulfillment queue — the voucher / instructions arrive right on the page; cancel any time before approval (auto-refund). Evaluation (Administrative, managers): per-member XP / activity / medals / recognition / redemptions for any range, with CSV export.
• Recognition (profile menu → Progress & rewards): spend your medals and trophies on a gift for a colleague (High Five → Lifetime Achievement Award, each with a price) with a post that can embed your item cards; start a pool so the whole team chips in (hidden from the recipient until it funds; unfunded pools refund after two weeks); announcers can start a vote with a prize paid up front — secret ballots, the most voted wins. Gifts land in the colleague's Inventory with a toast, a bell and a "You've been recognized" reminder; giving earns a little XP.
• Integrity (Administrative, managers): your reports' fair-play record — deleted-right-after-earning points are auto-returned, daily earning limits apply past a threshold (the action always works, only points pause), and any void or earning pause is visible to the affected person on their own timeline. "Repeat" badge = voided more than once; the Boss field defines whose record you see. Wrong call? A void is fully reversible on appeal — everything comes back, visibly.

Slide 5 — Logging in

• Email + password, or Sign in with Google.
• New users sign up directly, or arrive via an invitation email.
• Forgot password → reset link to your inbox.

Slide 5b — Forgot password, confirming your email, cookies

• Forgot password? → email → Reset Your Password page → new password twice → Change password.
• The link works once, for 60 minutes; resetting signs you out everywhere.
• Confirm your email from the link you receive; lost it? My profile → Resend confirmation.
• The confirmation page says confirmed, already confirmed or invalid or expired.
• Admins: System → Users → a person → Reset password / Resend confirmation (emails them a link).
• Cookie banner: Google Analytics only starts after you allow Analytics Cookies.

Slide 6 — Accepting an invitation

• Invitation lands in your email.
• Click the link.
• If you don't have an ALMAS account: the link goes to a sign-up form.
• If you do have one: a one-click "Accept to join?" dialog.

Slide 7 — Creating a tenant

• Top-bar tenant switcher → Add new tenant.
• Fill name + optional avatar.
• You become its first owner and admin.

Slide 8 — The notifications bell

• Bell shows unread count.
• Click to open the panel: 10 newest items.
• Real-time delivery — no refresh needed.
• Click an item to jump to the source (achievements → My profile → Achievements, podium → Leaderboard, recognition → Recognition, rewards → Rewards); click the trash to dismiss.

Slide 9 — The profile menu

• My profile · My timeline · My Favorites — always one click away.
• Progress & rewards ▸ Achievements · Leaderboard · Quests · Recognition · Rewards — opens in place; the progress pages also share a row of tabs.
• Help ▸ Get the Android app · Getting started checklist · Guided tours · Help center · What's new.
• Flags — instant language switch: English, Português (Brasil), Español.
• Log Out.
• My profile groups your own settings: Account (General, Info, Social links) · Security & access (Change password, API Keys, AlmasFS) · Preferences (Shortcuts, Floating buttons) · Progress (Achievements, Inventory).
• Tenant settings (admins only) moved to the tenant menu — click the workspace name next to your avatar.
• If emails to you bounce: a yellow box under E-mail in My profile → General and an amber envelope reminder. Automatic emails pause one week at a time; four bounced weeks in a row stop them. Fix the address and save, or click Resume emails. Password resets and invitations always arrive.

Slide 10 — Where to get help

• Help center — profile menu → Help → Help center (also linked in the footer) — articles + FAQ.
• User Manual doc — the long-form reference.
• Support module — file a ticket internally.
• Bug reporting — N B or the Report button on any error.
• The same manual, course and FAQ are also published as plain web pages at www.almas.cloud/help — handy for reading on a phone, sharing a link with a colleague, or asking an AI assistant about ALMAS.

Slide 11 — Two-key sequences, not chords

• Press the first key, release, then press the second. No holding.
• Three families: G (go to), N (new), T (tenant).
• Press ? from anywhere to see the full list in a modal.

Slide 12 — Navigate and create

• G D Dashboard / G T Tasks / G P Projects / G C Companies / G I Invoices / G R Transactions / G U Users / G L Lawsuits.
• N T Task / N P Project / N C Company / N I Invoice / N R Transaction / N L Lawsuit / N B Bug.
• S S focus the search box.

Slide 13 — Tenant switching

• T 0 personal workspace.
• T 1–T 6 your six pinned tenant slots.
• Reorder slots in My profile.

Slide 14 — Dashboard at a glance

• Active tasks assigned to you.
• Year-to-date revenue, expenses, ARR, OPEX, balance.
• Revenue / expense time-series chart.
• Where money goes (expense pie) and comes from (revenue pie).
• Date-range selector top right.

Slide 15 — Working with projects

• Projects group everything: tasks, files, contracts, invoices, transactions, members.
• Create with N P. Sub-projects supported (set parent).
• Acronym field: a short code (e.g. Apollo Platform → AP). Leave blank → auto-generated from the name; editable; unique per workspace. Becomes the prefix of the project's task ids and shows in labels as <acronym> - Customer - Name.
• View has tabs for each related collection + Gantt toggle.

Slide 15b — Project pipelines

• Pick a project type on create — it sets the pipeline the project follows.
• Product Development pipeline: Intake → Problem Statement → PRD → Architecture → Planning → Implementation → QA → UAT → Release → Support → Closed.
• Each step can auto-create a checklist task (entering PRD → "Write PRD").
• Move with the pipeline buttons on the detail page: Advance / Ship / Close + status Pause / Block / Wait / Flag crisis / Resume.
• Gates: Advance is blocked until the step's tasks are done (a message lists what's left).
• Send back: from a late step, bounce the project to the exact earlier step that owns the problem (e.g. UAT → Architecture). Never skips forward.

Slide 16 — Working with tasks

• Two-pane layout: date filter on left, group-by tabs on top.
• Filters: All / Today / Next 7 / 7–14 / Overdue.
• Group by: Customer / Project / Tag.
• Create with N T. Bug = N B.
• Readable id for project tasks: <acronym>-<year letter>-<number>, e.g. AP-F-1 (AP project · F = 2026 · 1 = first task that year; the number restarts each January). Non-project / older tasks just show their plain number.
• AKA (nickname): optional short label, shows as a highlighted (nickname) badge before the task name; editable any time and never changes the id.

Slide 16b — Kanban view for tasks

• Two entry points: Show kanban on the global tasks list (all tasks) or View as ▾ → Kanban in a project's Tasks tab (just that project's tasks).
• The View as dropdown in the Tasks tab also offers Gantt — same button, two destinations.
• Same board both ways — only the data loaded differs.
• One column per workflow state (Unassigned, Active, On going, Pending, Waiting, Blocked, Concluded, Reopened, Closed, Canceled).
• Drag a card across columns to change its status — same effect as the Status dropdown on the task detail page.
• Illegal targets dim out the moment you pick up a card; the board only lets you drop where the workflow allows.
• Server-side rejection (no permission, raced edit, side-effect failure) snaps the card back and shows the reason.
• Read-only for users without update task — the board still loads, but every column dims on drag.
• Breadcrumb returns you to the project's Tasks tab in one click (it carries an anchor to the Tasks tab so you don't have to re-select it).

Slide 17 — Companies = clients, partners, suppliers

• Three tabs in the same module.
• Search box per tab.
• Create with N C.
• Detail view shows every linked invoice, contract, transaction, note.

Slide 18 — Contracts: ARR vs OPEX

• ARR = your tenant is the contractor (recurring revenue).
• OPEX = your tenant is the hirer (recurring cost).
• Same record, different sides.
• Templates module saves reusable contract bodies.

Slide 19 — Invoices

• Status flow: draft → sent → paid (or cancelled / overdue).
• Line items auto-total.
• Print → PDF.
• Public link (/external/invoices/{code}) for customers with no login.
• PIX QR code for Brazilian instant payment.

Slide 20 — Transactions

• A single money movement: in or out, in any currency, on a date.
• Create with N R.
• Attach a receipt; link to a project/company/invoice/asset.
• Cancelled transactions are hidden from totals but still visible.

Slide 20a — Reimbursements

• Under Accounting → Reimbursements — a report groups multiple expense lines an employee paid out-of-pocket.
• Each report needs a parent (Project / Lawsuit / Company / User) so finance can charge the right cost centre.
• Three ways to add lines:
  • Add line — manual entry.
  • Upload receipt — drop one or many photos/PDFs; AI extracts fields per file, each becomes its own line. Fix any misread values afterward with the pencil icon (adds a small ✎ manual badge to the corrected row).
  • Email forwarding — personal reimbursement+…@<tenant-inbound-domain> address auto-files receipts; free-form hints in the email body steer the AI when there's more than one candidate report.
• Totals show approved value with requested in parens when they differ; declined/excluded lines are excluded from totals.
• Forwarded emails card on the detail page lists every email that landed on this report (received / from / subject / status). Each row shows a paperclip chip per attachment; the chip for the file that became the reimbursement line is green, others stay gray and are still clickable for preview. Receipts that arrive inline in the email body (Cinemark, Fandango, web-store confirmations) get a synthesized "body PDF" chip marked (body) so the user can verify what the AI analyzed. A per-row Reprocess button retries after fixing a misconfig.
• Paperclip icon on each line links to attached files (receipt + email-body context).
• Workflow (Pending → Approved → Paid) is per-tenant and customisable under Tenant settings → Workflows.

Slide 20b — Transactions that contain other transactions

• Some transactions are masters that group child line items (reimbursement reports today; future kinds will follow the same pattern).
• Accounting → Transactions list shows masters only — line items are hidden so totals don't double-count. They're still reachable via the master.
• Sitemap/branching icon next to a row's vendor = "this transaction contains line items."
• On the master detail page a Transactions tab appears between Discussion and Activity, listing the children.
• Reimbursement-kind masters clicked from the Transactions list open the dedicated Reimbursement detail page; the breadcrumb remembers you came from Transactions so you can navigate back.

Slide 21 — Sales pipeline

• Track deals through stages: lead → qualified → proposal → won / lost.
• Filters by status, priority, expected close date.
• Status badge shows stage at a glance.

Slide 22 — Inventory and products

• Products = flat catalogue.
• Inventories = stock per product per location.
• Movements (receive, issue, transfer, adjust) are recorded with timestamps.
• Low-stock thresholds trigger alerts.

Slide 23 — Lawsuits

• Track legal cases with parties, status, jurisdiction.
• Timeline of every action with timestamps.
• Documents attached per case.

Slide 24 — Files and storage

• Drag a file onto any entity's Files tab to upload.
• Storage cap per plan; usage visible in Tenant settings → Storage.
• Files inherit permissions from their parent entity.
• Downloads use 15-minute signed URLs (refresh page if a link expires).

Slide 25 — The three permission levels

• Read-only — browse and view.
• Read-write — read-only + edit, add notes, upload files.
• Admin — read-write + delete, manage members, change ACL.
• Applies to: projects, tasks, files, contracts, invoices, lawsuits.

Slide 26 — How to share a record

• Open the record → Share button.
• Pick users or whole teams.
• Pick a level for each.
• Save.

Slide 27 — Inheritance

• Sharing a project cascades to its files, notes, tasks, sub-projects.
• Sharing with a team grants the same level to every member.
• Members tab shows everyone with access and how they got it.

Slide 28 — Teams

• Named groups of users for easier ACL management.
• Each team has members + assigned permissions.
• Deactivate a team to revoke access without deleting it.

Slide 29 — Roles and the permission matrix

• A role = a named bundle of (resource × action) checkboxes.
• Defaults: Admin / Manager / Member / Viewer.
• Clone an existing role to start from something close.
• Assign per user or at invitation time.

Slide 30 — Inviting people

• Sidebar → Invitations → Send invitation.
• Email + role + optional message + optional expiry.
• ALMAS auto-detects: new user gets sign-up flow, existing user gets one-click join.
• Bulk invite via CSV upload.

Slide 31 — Email-to-note

• Send email to {tenant}+{entity}_{id}@almas.cloud.
• Body becomes the note; attachments uploaded to storage and linked.
• Polled every 5 minutes.
• Tenant admins set allowed_sender_emails / allowed_sender_domains.

Slide 32 — Internal support tickets

• Sidebar → Support.
• Title, description, priority, assignee.
• Filters: status, priority, age.
• Discussion thread per ticket.

Slide 33 — External (public) support tickets

• Customers submit through /external/support — no login.
• Form: name, description, priority, optional tags + attachments (10 MB max).
• Tickets land in Support, assigned to the tenant owner, marked task type Support.

Slide 34 — Announcements

• Broadcast a message to all users / specific roles / specific teams.
• Rich text body + scheduled publish date + expiry.
• Recipients see a modal on next page load + an entry in notifications.

Slide 35 — Workflows

• Trigger (event, schedule, or manual) → conditions → actions.
• Actions: send email, update field, create record, post to webhook.
• Test mode for dry-runs. Execution history per run.

Slide 36 — AI features are premium

• AI Agent and AI File Analysis require a plan that includes AI.
• Greyed-out menu items show a Premium feature dialog with View plans.
• Tenant admins can override per-tenant.

Slide 37 — AI File Analysis

• Drag any file (PDF, image, scan, spreadsheet) onto the drop zone in the top bar.
• AI detects type (invoice, contract, receipt, report).
• Suggests an action: create transaction, create invoice, update existing, create contract.
• For invoices/bills: shows similar past records to avoid duplicates.
• After action runs, file is auto-attached.

Slide 38 — AI Agent: chat with your data

• Open from the sidebar (premium + permission required).
• Ask in natural language: "Which projects were profitable in 2025?", "Create a follow-up task for Acme."
• Response: markdown answer + expandable tool-call panels + token cost.
• Sessions are saved — resume any past chat.

Slide 39 — Agent permission scope

• Agent runs as you — no escalation.
• Can only see / change what you can see / change.
• Refuses actions you couldn't perform manually.

Slide 40 — AI bug triage

• Every bug you file gets an AI fix-plan note within ~1 minute.
• Plan covers: summary, repro steps, suspected cause, proposed change, test plan — formatted for the dev team.
• Dedup: same bug twice in 30 days → second linked instead of re-run.
• Rate limit: 5 plans / user / hour.

Slide 41 — Two entry points, one pipeline

• N then B (sequential keys) — opens the report modal anywhere in the app.
• The Report button on any error popup — auto-fills from the failure.
• Bug or Feature: the modal has a type selector. Bug = report something broken; Feature = request something new. Both create a task and both get an AI-written plan note (fix plan for a bug; impact/approach + suggested size & priority for a feature).
• On submit you get a quick ✓ Task created confirmation; the plan note lands on the task ~1 minute later.
• Both attach a rich context bundle to the task invisibly.

Slide 42 — What gets captured automatically

• The page URL and route you were on.
• Your last ~50 navigations (breadcrumbs).
• Your last ~10 API calls (sanitized — passwords and tokens stripped).
• Any browser console errors from your session.
• Browser, viewport, timezone, language.
• The error details, when filed via the Report button.

Slide 43 — What you have to do

• Title: short and concrete.
• Priority: pick honestly; the AI runs regardless.
• Description: optional. Add expected-vs-actual if it isn't obvious.
• Hit Save. Done.

Slide 44 — What you'll get back

• A note on the bug titled "AI Triage Plan" with these sections:
  • Bug summary
  • Reproduction steps
  • Suspected cause
  • Proposed change
  • Test plan
  • Verification steps
• A second attachment with the raw context bundle, in case the team needs to dig deeper.

Slide 45 — Guard rails to know about

• Dedup: identical bug filed twice within 30 days → second one is linked, not re-run.
• Rate limit: 5 AI triages per user per hour. Beyond that, bugs are still created — just without an auto-plan.
• Redaction: Authorization headers, cookies, password/token/secret fields are scrubbed before leaving your browser.
• Size limits: response bodies > 8 KB are truncated with a marker.

Slide 46 — What NOT to do

• Don't put passwords, API keys, or customer PII in the title/description (they aren't auto-redacted there — only HTTP headers and structured fields are).
• Don't file the same bug repeatedly to "get faster service" — dedup just links them.
• Don't disable the error popup just to avoid the noise — the Report button is the most context-rich way to file.

Slide 47 — Changelog page

• Footer shows your current version (e.g. Version 0.9.1-45).
• Click the version number → Changelog page.
• Releases listed newest-first; latest highlighted with a colored border.
• Categories per release: Added · Changed · Fixed · Security · Deprecated · Removed.
• Bullets tagged [backend] (server / data / APIs) or [frontend] (UI you see).
• "Load older releases" reveals more on demand — no infinite scroll surprises.
• "Full changelog" button downloads the entire history as a markdown file.

Slide 47a — Why mount your tenant

• ALMAS data appears as a regular folder on your computer.
• Drag-drop files into a project from Explorer / Finder, no upload screen.
• Open notes in your Favorite text editor; save Word docs back into a project.
• Works on Windows, macOS, Linux — anything that speaks WebDAV.

Slide 47b — Generate a token

• Top-right avatar → AlmasFS Access.
• Name it (e.g. "Office laptop") + pick expiry.
• Copy the token immediately — shown once only.
• Treat it like a password. Anyone with it gets your AlmasFS access.

Slide 47c — Mount

• See Help → AlmasFS for platform-specific instructions:
  • Windows: net use Z: <URL> /user:<email> "<token>" (after a one-time registry tweak)
  • macOS: Finder → Connect to Server → paste the URL
  • Linux: mount.davfs2 or your file manager's WebDAV support
• Your username is your email, your password is the token.

Slide 47d — Living with the mount

• Drag-drop files in, edit notes in Notepad, Save in Word — all works.
• F2 to rename a project. Del to soft-delete.
• Revoke any token you no longer recognise from the AlmasFS Access page.
• COPY between folders isn't supported yet — download and re-upload for now.

Slide 47e — What an API key is

• A long-lived password-replacement you give to a tool or assistant so it can act in ALMAS as you.
• Looks like almas_live_… — a single bearer token, no separate username.
• Bound to one tenant and a subset of your permissions — never grants more than you have.
• Issued from My profile → Security & access → API Keys (or /profile/api-keys).

Slide 47f — When you'd create one

• Connecting a payment provider's webhook (Stripe, PayPal) so it can record transactions automatically.
• Hooking up a bookkeeping tool that reads invoices on a schedule.
• Giving an AI assistant (Claude, custom GPT) read or write access over MCP.
• Wiring up a one-off export script, a Zapier-style automation, or a custom dashboard.

Slide 47g — Creating your first key

• New key button on the API Keys page.
• Name — describe what it's for (Stripe webhook, not key1).
• Tenant — pick one. One key, one tenant, for life. Multiple tenants → multiple keys.
• Permissions — mirror mine (follows your role over time) or pick specific (frozen at creation).
• Expiry — 30 / 90 / 365 days. No "never expires" option.
• Optional — IP allowlist (CIDR-style) and a per-key rate limit.
• Copy the secret immediately — it's shown once. ALMAS only stores a hash.

Slide 47h — Mirror vs. specific permissions

• Mirror my permissions — the key always has what you have today.
  • You lose delete invoice → the key loses it within seconds.
  • You gain read transaction → the key gains it too.
  • Best for general-purpose integrations where access should track your role.
• Pick specific permissions — abilities locked at creation, never grow.
  • Future-proof against scope creep ("the bookkeeping tool will never delete things").
  • Narrow keys are safer if leaked.
  • Best for single-purpose webhooks and scripts.
• Rule of thumb: pick specific by default; pick mirror only when the integration legitimately needs to follow your role.

Slide 47i — Rotation and revocation

• Rotate — issues a fresh secret on the same key. Old secret keeps working during a grace window (default 24h, up to 7d) so you have time to update the integration without downtime.
• Rotate when: a vendor leaked credentials, quarterly per policy, employee with access left, you lost the original secret.
• Revoke — immediate kill switch. No grace window. Every request using the key gets 401 from the next call onward.
• Revoke when: you suspect a leak, the vendor no longer needs access, you're decommissioning the integration.
• Revoked keys remain visible in the list as an audit trail; you cannot un-revoke (create a new key instead).

Slide 47j — Common pitfalls

• Sharing the secret in chat / email — treat it like a password. Use a password manager or secrets vault.
• Forgetting expiry — ALMAS won't email you ahead of time today. Calendar a rotation reminder when you create a key with 90+ day expiry.
• 401 errors — key wrong / expired / revoked / past its rotation grace window. Check the list status.
• 403 errors — key valid, but action not permitted. Either the key's abilities are too narrow, or you yourself lost the permission. Check the key's effective permissions on the detail page.
• 429 errors — per-key rate limit hit. Means the integration is mis-configured (infinite loop, aggressive polling). Investigate before raising the limit.
• Connecting an AI agent — same key works for MCP. Paste the snippet from your AI client's docs, use your key as the Authorization header. If the agent reports "0 tools available," the key has no abilities — check its permission set.

Slide 45a — The 30-day safety net

• System → Tenants → red × icon → a confirmation page (not a modal) opens.
• The page lists exactly what soft-delete means and gives you a 30-day window to undo.
• To unlock the Delete tenant button you must type Delete! (capital D, exclamation mark) into the input — misclicks are physically impossible.
• After delete the tenant shows a yellow Pending purge (Nd) badge on the list. Click the green undo to restore at any point in the 30-day window.

Slide 45b — Export before delete

• The confirmation page has a Start a full export before deleting toggle. Leave it on unless you're certain you'll never need the data back.
• The export job produces a zip with every table and every file, uploads it to storage, and emails you a signed download link valid for 30 days.
• You can also start an export from the per-row download icon on System → Tenants at any time, independent of delete.

Slide 45c — Import a tenant from a backup zip

• System → Tenants → New → toggle Import from a tenant backup zip → pick the zip.
• The new tenant always gets a brand-new ID (the original is never reused).
• You'll receive an email when the import completes; the tenant becomes usable as soon as the email lands.

Slide 48 — Account hygiene

• Set a strong password and turn on 2FA in My profile.
• Pick your default language so future sessions land in it.
• Pin your most-used tenants in slots 1–6 for fast switching.
• Set your avatar — makes you findable in @-mentions and assignment pickers.
• Keep your e-mail address current. If it starts bouncing, ALMAS pauses automatic emails to you and says so in My profile.

Slide 49 — Where to go next

• Skim the User Manual sections that match what you'll use most.
• Open ? everywhere — there are more shortcuts than you can memorise on day 1.
• Star the dashboard and check it once a day for active tasks + financial pulse.
• File the first small bug you find — the AI triage will give the team a fast feedback loop.

Slide 50 — Q&A

• Open floor.
• Common questions to seed the discussion if it stalls:
  • "How do I share a project with someone outside my tenant?" → invite them, then share the project.
  • "Why is the AI Agent greyed out?" → plan doesn't include it; see the Plans page.
  • "Can I bulk-invite my whole team?" → yes, CSV upload in Invitations.
  • "Where do my files go?" → tenant-isolated cloud storage; downloads via signed URLs.

Slide — What's the difference?

• Pin (📌) — Whole tenant sees it pinned. Floats to the top of its list.
• Favorite (❤️) — Only you see it. Personal bookmark. Spans every tenant you're in.
• Same icons, different visibility. One is for the team; one is for you.

Slide — Where to click

• Each note in a discussion thread has the pin + heart icons next to its timestamp.
• Click pin → goes amber, note jumps to top for everyone.
• Click heart → goes red, note added to your personal "My Favorites" list.
• Click again to undo.

Slide — "My Favorites" page

• Top-right avatar dropdown → My Favorites.
• Shows everything you've Favorited across every tenant you belong to in one view.
• Grouped by tenant. Click an entry to deep-link into that tenant.
• Filter buttons: All / Notes / Projects / Tasks.

Slide — Etiquette

• Pin sparingly — if everything is pinned, nothing is.
• Favorites are private — your manager doesn't see what you've Favorited.
• Removing yourself from a tenant cleans up Favorites there automatically.

Slide — Who this is for

• System administrators only. The tabs below appear only with the system-admin role.
• The System dashboard charts are now grouped into tabs: Operations / Development / Deploy.

Slide — Operations tab

• The charts you already had: live WebSocket connections, storage growth, AI usage, API-key usage.
• Nothing moved or changed — just tidied under one tab.

Slide — Operations tab: who is active (new)

• Opens on the last 7 days; the range buttons (7 Days … 3 Years, or your own dates) drive every card.
• Activity card: unique logins, new users (+ portal contacts apart), new tenants, average connection time.
• A table per tenant: connected people, sessions, average and total time — busiest on top.
• Unique Users on the connections card.
• Storage added per tenant (30 days) pie: who uploaded the most this month.

Slide — Operations tab: see every AI call (new)

• Click Total, Successful or Failed AI calls → the list of those calls (tenant, person, feature, model, cost).
• Filter by status, tenant, feature; search errors, models, people.
• Click a call: failed → the error; successful → the request and the AI's response; always what triggered it.
• Call text is removed after 90 days; the numbers stay.

Slide — Development tab

• Visualises every ALMAS commit since Jan 2020, classified by type (feature / bug fix / UI / …).
• Summary cards: total commits + lines of code for the API and the web app.
• Commits per month bar chart — click a bar to drill into that month's commits (type, area, summary, lines).
• More charts: features, bug fixes, UI work, work-mix, lines of code; plus a milestone timeline.
• Refresh button rescans for new commits; charts update themselves when it finishes.

Slide — Deploy tab (1/2)

• One-click application update — what an engineer would do from a server, guided.
• Check for updates → plain-English summary + a table of changes (commits, migrations, steps). Preview only; nothing changes yet.

Slide — Deploy tab (2/2)

• Deploy → you must type the target branch name to confirm (a deliberate speed-bump).
• A live log streams each step; on success you see the changelog and the Development charts auto-refresh.
• Deployment history records every past deploy (who/when/result); Rollback reverts the last one.
• Download latest run log (top of the history) → the full record of the last update, started here or on the server, plus a one-line Last run status. Send it to support or an AI agent when an update reports problems; passwords and keys are masked.
• Serverless note: on fully serverless hosting the deploy button shows "not available here" — those update via their own pipeline.

Slide — Permissions

• Viewing Development = the system-admin role.
• Deploying = a separate, stronger permission. Greyed-out Deploy buttons mean you can look but not deploy.

Slide — The idea

• ALMAS never quietly throws away data that other records depend on.
• When a delete or rename would cause a problem, it stops and asks — showing exactly what's at stake.
• You always get a clear proceed or cancel choice. Nothing happens until you confirm.

Slide — Rename onto a deleted company

• Rename a company to a name that belonged to one you deleted earlier → ALMAS recognises it.
• Dialog: "A deleted company named Acme already exists. Restore it instead?"
• Restore brings the old one back (no duplicate); Cancel lets you pick another name.
• Renaming onto a still-active name → simple "name already taken" message instead.

Slide — Delete a company with related records

• Company has projects / invoices / transactions / contracts / contacts → ALMAS warns first.
• Dialog lists the counts: "• 4 projects • 2 invoices … Delete anyway?"
• Delete anyway to proceed; Cancel to keep it.
• The first/root company can never be deleted — by design.

Slide — Delete a product that has stock

• Product still shows inventory → ALMAS asks before removing it.
• Dialog: "This product still has 37 unit(s) in stock. Zero the inventory and delete it?"
• Zero & delete does both in one step; Cancel keeps it if the count looks wrong.

Slide — Deleted companies in transactions and projects

• Delete a company that transactions or projects point to → those records still work.
• The company name still appears with "(deleted)" after it, and it's no longer clickable (nothing left to open) — your financial history and project lists never go blank.

Slide — Drag a file onto the Files card

• The Files card accepts dropped files. Drag over → a dashed "Drop files to attach" area appears. Drop → the Add File window opens pre-filled.
• The usual "add file" button still works; drag-drop is just faster. Visible only where you can edit.

Slide — No Files card yet? Drop on the Description

• On projects, tasks, lawsuits, and transactions the Files card is hidden until a record has files.
• When it's hidden, drag your file onto the Description card instead — it lights up, you drop, confirm, and the Files card then appears.

Slide — Select many tasks at once

• The task-row checkbox now selects the task (it no longer marks it done by itself).
• Finished tasks are shown struck through.
• A selection banner shows the count, with Select all / Deselect all on its left (acts on the tasks currently shown).
• The buttons adapt: Mark done when something isn't finished yet, Reopen when something is already done (both if your selection is mixed).

Slide — Right-click a task

• Right-click a task row → a menu at your cursor: Mark done / Reopen, Pin, Favorite, Edit.
• The ⋯ (three-dot) menu on each row also has Mark as done / Reopen.

Slide — Your task filters stick

• Filter the task list (status, or the Customers / Projects / Tags tabs) and it's remembered.
• Leave the page and come back → same filters, until you log out or close the tab.

Slide — Four health cards on your dashboard

• Top of the dashboard: Gross Margin, Rule of 40, Sales Efficiency, LTV / CAC — a 12-month snapshot of business health.
• Click a card to expand the details (the figures behind the number).

Slide — Why a card might be blank

• A card shows a dash (—) with a short reason when it can't be calculated yet, e.g. "needs expenses classified as Sales & Marketing."
• ALMAS won't show a misleading number — it tells you what's missing instead. The fix is sorting expenses into categories (next slide).

Slide — Sorting expenses (administrators)

• System → Expense categories (system administrators only).
• Each expense gets a category: COGS / Sales & Marketing / G&A / Other / Revenue. Pick from the dropdown — it saves instantly.
• Categories are shared across the whole organization, which is why they're admin-only — and they're what power the health cards.

Slide — The automatic "Popular" tag

• ALMAS tags the most-viewed projects, tasks, invoices, lawsuits, and assets with a "Popular" tag, refreshed daily.
• Nothing to switch on — items that cool off lose the tag automatically. Use it to see what your team is focused on.

Slide — Contact types on companies

• Adding/editing a company contact now has a Type: Financial / Technical / Commercial / Manager / Legal.
• A badge on the company detail page shows each contact's type at a glance. Optional — old contacts show no badge until you set one.

Slide — Export a list to CSV

• List pages now have an Export CSV button — downloads the current list as a spreadsheet file (Excel / Sheets / Calc).
• Only shows data you can see, only for the organization you're in.
• Files are prepared to be safe to open; a leading ' in front of = + - @ cells is the safety measure, not a typo.
• Companies has it first; more pages follow.

Slide — Sign-in messages

• Wrong email/password → "These credentials do not match our records." shown right on the login form.
• Too many wrong tries → "Too many login attempts. Please try again later." — sign-in pauses ~15 min to block guessing. Wait, then use the correct password (or reset it).
• Change your password: My profile → Change password → current password, new one twice (8+ characters) → Change password.
• It signs you out everywhere, this browser included — log in again with the new one.
• A wrong current password shows under that field. Ten tries a minute, then wait.
• Only you can change your password — not an admin, not an API key.

Slide — When ALMAS is briefly unavailable

• During an update ALMAS can be unavailable for a minute or two.
• The app waits and retries on its own, more slowly each time — no need to keep clicking.
• Afterwards the next click just works, no reload.
• Saved something and saw an error in that minute? Save again. A page didn't load? Open it again.

Slide — Pins now stick

• Pin / favorite a task and it stays after a refresh or when you return later (previously it could look like it vanished — now fixed).

Slide — A faster task list

• Type icons before each task — bug = defect, star = feature, flag = milestone, generic icon for the rest.
• Sort dropdown: Created date / Priority (default) / Status. Ties always break alphabetically by name.
• Search box filters by id / name / project, instantly, in the browser.
• Your sort + search choices are remembered across reloads.

Slide — Confirmation when you create

• Creating a task, project, company, invoice, contract, transaction, or lawsuit pops a toast: "✓ created — ."
• Open jumps straight to the new record; Copy link copies its URL to share (shows a brief "Copied").
• Fades on its own after a few seconds, or dismiss it.

Slide — More room for descriptions

• The Description field on task and bug create now grows well past the old 5-line limit.
• When it gets very tall it scrolls inside the box instead of pushing Save off-screen.

Slide — Refreshed Kanban board

• Now legible in dark mode — cards, columns, and the dragged card all stay readable.
• On narrow screens columns scroll sideways instead of squashing.
• How you use it is unchanged — drag cards between columns as before.

Slide — See if everything's running

• New System status page in the Help center (Help → System status).
• A traffic-light: green = all good, yellow = degraded, red = a service is disrupted.
• Per-area colours for Database, Tenant databases, Background jobs, Cache, File storage, Realtime.
• A 7-day history strip per area shows whether a hiccup is current or already passed.
• Read-only and safe — a quick way to tell if a problem is on your side or ours.

• Administrative → Hiring → New hire, pick the Hiring type. The hire moves through stages: Position request → Approval → Job description → … → Onboarding → Hired.
• At Job description, pick the role, then choose Approve — hire a human or Approve — hire an AI employee.
• AI path: at Configure, set the model (or click Generate from a résumé/JD to auto-fill role + skills), then Save & provision agent — a new AI team member is created.
• The Agents tab lists your AI employees, their role, and status (new ones start pending).
• AI employees work on projects, tasks, companies and campaigns — they never manage users, roles, invitations, teams, workflows, plans or tenant settings, never hire other AI employees, never delete.
• Stuck on a stage ("open tasks")? Finish that stage's task — the gate prevents skipping work.

Slide — Give a task an owner

• Every task can have an assignee: a person, a team, or an AI employee.
• New task form → optional Assignee picker (people + teams). Empty = unassigned, anyone can pick it up.
• On a task, the Assignee card shows who's on it (an AI badge for an AI employee, a Team badge for a team); Assign changes it.

Slide — Your inbox + the review loop

• Tasks assigned to you or your team are your inbox — your queue. AI employees use the same inbox.
• Done? Submit for review → task goes to In Review.
• A reviewer clicks Approve (→ Concluded, the stage can move on) or Request changes (→ Changes Requested, comes back to be fixed and resubmitted).
• Auto-assignment: skill-tagged tasks created by a stage are routed to a matching AI employee (prior-project one preferred); no match = left for a person.

Slide — Type icons + tooltips

• Every card shows a distinct icon per task type (bug, feature, milestone, epic, story, …) before the name.
• Hover any icon for a tooltip naming the type — even unrecognised types show an icon and a tooltip.

Slide — One Filters menu + standalone search

• Status, type, priority, assignee, sort are grouped under a single Filters button.
• New assignee filter — show only tasks owned by a person, team, or AI employee.
• Search sits on its own beside Filters and View; type to narrow the list instantly (no reload). Clear to restore.
• Export XLS now lives inside the View as menu, next to list/kanban.
• Picking the blank/"all" status now shows every task again.

Slide — Edit name + description in place

• Pencil icons next to the task name and description turn each into an editable box with Save / Cancel.
• Navigate away or refresh mid-edit? Your unsaved text is remembered and restored when you return.
• Pencils appear only if your role can edit tasks.
• The assignee chip is unchanged for you (AI / Team badges still shown) — just loads leaner behind the scenes.

Slide — Attach a link as a file

• Add File now has an Upload File / Add Link toggle.
• Add Link = attach a web address (Google Doc, Figma, shared folder) with a title + optional description instead of uploading.
• Links sit in the file list with your uploads; click to open; edit a link's address/title/description anytime.

Slide — Pin & favorite files

• Every file now has the same controls as notes/tasks: pin (📌 amber, top for everyone) and heart (♥ red, your favorite).
• Both stick after refresh.

Slide — Lifecycle timeline on projects & tasks

• A thin colored progress bar near the top of a project/task shows the stages it's been through.
• Segment width = time spent in that stage; ticks = stage changes.
• Hover a segment for stage name, dates, duration, and who moved it.
• Big phase labels — Pre-sales / Sales / Deployment / Support — sit where the project entered each phase. Read-only, no setup.

Slide — Subproject tree + Flatten

• Projects with subprojects show as an expandable tree on the Projects list — click a parent to drill in.
• Flatten toggle collapses it to a plain flat list; toggle back for the tree.
• Search and filters work either way — search reaches nested subprojects.

Slide — Staff view

• New Staff view (Administrative) merges Users + AI employees + open positions in one place.
• Tabs: People / AI Agents / All. The Role column shows each person's role here.
• An admin manages a person in this workspace: role, job, boss, salary, status, name, phone, photo.
• An admin cannot: change their email or password, open people who are not members, or delete the account — remove them from the workspace instead.
• A row shows a small amber pause badge (red stop after four weeks) when emails to that person are bouncing; hover it for details. Their page has an Email delivery line: OK, Paused until a date, or Stopped. Admins can click Resume emails there.

Slide — Dashboard quick actions

• The Dashboard has big quick-action tiles: New Project / New Task / New Invoice — one click into the create flow.

Slide — Deal-lost reason + Sales Funnel

• Moving a sales project to Lost prompts for a short reason — kept with the project, shown in its history.
• New Sales → Funnel page: pipeline as a funnel by stage (Pre-sales/Sales/Deployment/Support) + won / in-progress / win-rate / lost KPIs.

Slide — Subscribe to an ALMAS calendar

• Calendar page (/admin/calendar): tick the date types (Tasks/Projects/Invoices/Transactions), optionally a single project, click Generate.
• Copy the subscribe link into Google/Apple/Outlook calendar ("Add by URL") — your ALMAS dates refresh automatically.
• The link is private + secure: works without login (so your calendar can read it), shows only your org's dates, can't be tampered with. Share it like a password.

Slide — One list, people + AI

• Administrative → Workforce shows everyone — humans and AI employees — with a live status chip: green Online/Idle, blue Working, grey Offline, red Error.
• AI badge marks AI employees; current task + model show alongside; last seen shows recency.
• Top summary: worked hours this period, worker count, working now.

Slide — Live updates + premium

• Updates in real time — watch an AI employee flip Idle → Working (task appears) → Idle as it picks up and finishes work, no refresh.
• Premium feature (the ai_workers plan); AI employees appear once hired.

• Administrative → Capabilities: the role catalog behind hiring — create/edit roles; the slug is the permanent id; deleting is blocked while anyone holds the role.
• Workforce → Billed hours card: this month's AI-worker hours vs your plan allowance; red bar = over (warning by default; strict plans pause new AI work).

Slide — One inbox for everyone

• Sidebar Messages (or the top-bar mail icon with its unread dot): conversations on the left, thread on the right, presence dots live.
• Chat with AI employees like colleagues — they answer in the chat; big requests become tasks.
• One conversation per person across ALL shared workspaces; offline people get a notification.
• Start a chat from Workforce via the chat button on any row.

Slide — Who you can message

• Your list = the people the Staff page shows you in this workspace (everyone with team-wide visibility; otherwise the people you manage, plus whoever created your account).
• Someone who can see you may write first; once a conversation exists you can always answer.
• In a group, click the participant count: every member is listed, each one a click away from a direct conversation.
• A thread you cannot write from here shows You cannot start a conversation with this person from here — history stays readable.

• + New group in the Messages sidebar: title + tap names to add Writers (max 25).
• Announcement type = few writers, unlimited read-only listeners — company-wide broadcasts.
• Group threads show sender names; unread badges are per group; the top-bar mail dropdown includes groups.
• Export: download your whole chat history as a password-protected ZIP (account password asked first; SSO skips).

Slide — Grants and values

• Users → user → Credentials: which tools each person/AI is set up for (pending → active).
• Set value stores the key encrypted (lock + version); AI employees pick it up automatically; Rotate bumps the version.
• Reveal = re-enter your password, value shown once, always audited. Revoke deletes the stored key too.
• Needs manage credentials (tab) / reveal credentials (reveal).

Slide — Campaigns are projects with a marketing flow

• Marketing → Campaigns is the new home; a campaign is a project kind (notes, files, tasks, journal — all there).
• Pipeline: brief → proposal → approval → production → review → launch → running → closed. Approval and review are the steps you conclude.
• Objective, channels, dates, leader — and a planned budget that creates the budget with the ceiling on.
• Campaigns never show under Administrative → Projects.
• Permissions: read campaign to see, create/update campaign to act, all campaign for admins.

Slide — Budgets: plan, order, purchase, stay under the line

• Every project and campaign has a Budgets tab.
• Budget = planned amount + the items you intend to buy; mark items Ordered then Purchased.
• Bar = spent vs planned; Remaining = planned − actual − committed; items purchased x / y.
• Ceiling, three ways: Auto-block (refused), Soft-block (refused unless you write a justification), No block (always accepted, bar turns red).
• Pencil = edit — on a budget's name (plan, ceiling, description) or an item row. Edits face the same ceiling as new items, justification and all.
• A line awaiting approval cannot be edited — decide it first.
• Item form: Unit is the shared units dropdown; Vendor lists every company with a relation badge.
• A soft-block justification is kept on the line and in the budget's history — who went over, by how much, and why.
• Over-budget items need approval (soft-block only) → the justified item waits as Awaiting approval and counts nothing until someone clicks Approve; Decline drops it. The requester cannot approve their own.
• Budgets nest (campaign → per-channel sub-budgets); totals roll up. Under the hood they are transactions (branching icon in Accounting → Transactions).

Slide — Lead forms & tracked links

• Forms & links tab: build a form (fields + consent), copy its public URL or embed snippet.
• The public URL opens a ready-made page anyone can fill in without logging in — that is the link you share. The embed snippet is for putting the form on a site you already have; the form endpoint (JSON) underneath is for developers, not for sharing.
• A submission = a new lead at the first Sales step, with contact, source tag and the campaign as origin; the owner is notified; the campaign's Leads tab lists it.
• Tracked links = short public links that count clicks and add the campaign's UTM parameters — for posts, emails and QR codes.
• Attribution follows the deal to the contract and the invoice; Sales → Funnel groups by source.

Slide — Departments live on the pipeline step

• A project is one record from lead to deal to build to support. Nothing is copied or converted.
• Every pipeline step belongs to a department (Sales, Engineering, Support …). Move the step → the project changes board.
• Sales → Pipeline = projects on a sales step (the deal board). Administrative → Projects = engineering (+ Unassigned rows such as Closed). Support → Projects = support.
• The Department filter on the Projects list and the chip on cards / the project header show where a project sits.
• Classic step Waiting is now Procurement (a sales step). Leads captured by a marketing form follow the Solution flow: Prospection → … → Won → SoW → … → Delivered → Support.
• Send back when work has to return to an earlier department.

Slide — Legal matters on any project

• Project view → Legal tab → Open legal matter: the lawsuit is created as a child of the project and listed there; Legal → Lawsuits still lists everything.
• Works on a deployment, a deal or another lawsuit. A matter runs alongside the project — it never moves the project off its board.

Slide — A deal is won when it leaves sales

• The moment the project you lead moves from a sales step to an engineering step (Signed → SoW, Won → SoW, or a drag on Sales → Pipeline), you are credited a deal won — whoever moved it.
• Medals: First Blood (1) · Closer (10) · Rainmaker (50) · Kingmaker (200). Trophies for value sold: Six / Seven / Eight Figures (100k / 1M / 10M in the workspace currency, converted at the day's rate).
• Speed Run — won within 30 days of entering sales. Comeback Kid — sent back to sales, won anyway. Pipeline Builder — 25 leads moved past the first sales step.
• Once per project: bounce it back and win it again, nothing new. AI employees and system moves never earn.

Slide — Marketing medals

• Launch Day — first campaign goes live. Full Funnel — a lead your campaign captured becomes a won deal. Lead Magnet — 100 public form submissions.
• On Budget — 5 campaigns closed with their budget not over. Clean Sheet — 10 budgets closed with no override on any line.
• Everything shows on My profile → Achievements (progress bars on the locked ones) and the medals in your Inventory. Past deals can be credited retroactively by an administrator.

• Sidebar: Marketing → Audiences / Campaigns / Contacts / Dashboard.
• Dashboard: 15 tiles (funnel, spend & return, email & consent) + 3 charts; date range + campaign filter; a tile explains itself when it cannot be computed. Same tiles on a campaign's Results tab.
• Audiences: reusable filters over contacts; six seeded; Preview = count + masked sample; only contacts with email consent count.
• Contacts: one directory for company contacts and captured leads; consent chips (No consent / Opted in / Opted out / Suppressed); Opt in / Opt out; company contacts edited on the company page (name + email required).
• Campaign → Creatives: write or import HTML; live preview; Insert merge field; Save version; Send test to me; Approve (manage marketing). Keep {{unsubscribe_url}} in every email body.
• Campaign → Mailings: body + audience + subject → Submit for review → Approve → Send now / Schedule. The gate needs: campaign at launch, approved body, ≥ 1 recipient, sending not paused.
• Row counters: sent / delivered / opened / clicked / bounced / unsubscribed; Preview before sending.
• Unsubscribe / preferences links in every mailing; opted-out contacts are skipped automatically.
• Tenant menu → Tenant settings → Sending domain: register your domain, publish the CNAMEs, wait for verified; Brand = from-name, reply-to, footer address. Shared sender until then; automatic pause on spam complaints.

• Company page → Contacts card → Invite to portal (areas: Support tickets, Invoices) → contact signs up from the email.
• Mail lost? Copy invite link on the invited contact and share it yourself — recorded as shared manually by you; the signup then shows accepted via a link copied by … (audit trail).
• Contacts have a position from a standard list, grouped (C-Level, Finance, Engineering, …); one position can be in two groups (CFO = C-Level + Finance). Left empty, it is picked from the job title.
• Marketing → Contacts: Position column, Position group and Position filters; audiences filter by Contact position group.
• Audiences: Edit works on every audience, seeded ones too (name, filters, scope); seeded rows keep their tag and cannot be deleted.
• The customer sees only Tickets and Invoices for their company.
• Tickets: open with subject / description / priority / attachments; reply; close. Invoices: unpaid + paid, due dates, print link, PIX code + QR.
• Your team: Administrative → Support shows portal tickets with a Customer badge; every note is visible to the customer; status changes and notes notify them (portal + email).

• Three plans per company: Free (3 users, 2 GB, AI included), Team (15 users, 25 GB, AI employees, AlmasFS), Business (50 users, 100 GB, dedicated support).
• Every plan: all five departments, the AI assistant, MCP + API keys, no ads.
• Limits: 95% amber banner → 100% red banner, still works → +5% new activity on that limit pauses. Nothing saved is ever deleted.
• Plans → Pay as you go: add a card, switch it on, set a monthly cap — usage above the plan is billed per unit instead of being paused.
• Plans → Usage this month shows every limit and what it costs so far.
• Granted by ALMAS at the top = a plan given without charge; when it ends the workspace returns to its paid plan or Free. Some grants show usage but never pause.

• Hire: Administrative → Staff → New hire → Approve — AI → Configure: role Marketing Expert, tools from a list (Analytics, Canva, Meta Ads…).
• Add each tool's key on its Credentials tab; no key = not connected.
• Campaign steps assign it the marketing tasks (AI badge on Tasks): brief, plan + budget, creatives, audience, mailing, weekly report.
• Only people approve: budget, campaign plan, creatives, mailing, launch. The buttons never show for an AI employee; ALMAS refuses them anyway.
• It sends a mailing only once it is approved and the campaign is at launch, and publishes a landing page only once a person approved it.
• Its behaviour follows the role's playbook (Administrative → Capabilities) — edit it to set tone, channels and rules.
• Ask the Ghost: "how do I hire a marketing expert?" → guided tour.

• Marketing → Website: your public address sites.almas.cloud/your-address (suggested from your workspace name; claimed at the first publish).
• Create Website project → Creatives → + Creative → role Landing page.
• Building blocks: Lead form (with consent + WhatsApp opt-in boxes) and the WhatsApp chat link; no recipient fields, scripts are removed.
• Approve, then the globe publishes; first page = home; Live vN opens it.
• A later edit stays a draft (Newer draft not live) until approved + published again.
• Who filled the form: campaign Leads tab (email · phone · WhatsApp opt-in) and the Lead contact card on the lead's page (all answers + consent).
• Funnel per page: views → visitors → submissions → leads → conversion (Website page, campaign Results, dashboard Page views).
• Ask the Ghost: "how do I publish my website?"

• Tenant settings → WhatsApp: Business Account ID + Phone number ID + access token from Meta → Connect number (token stored encrypted, never shown).
• Only Meta-approved templates with body variables; Refresh templates after creating one in Meta.
• Mailings → + Mailing → WhatsApp → template → one contact field per {{1}}, {{2}}… → same review / approve / launch as email.
• Sent only to contacts with a phone and a WhatsApp opt-in (form box).
• Row shows sent · delivered · read · replied; replies become notes on the company; STOP removes WhatsApp only.