Skip to main content
Emma is designed to be careful with anything that leaves your workspace and thorough with everything inside it. This page sets out the boundaries she works within and what to do when her output isn’t right.

​
What Emma won’t do

  • Submit a bid or upload anything to a buyer’s portal.
  • Contact a buyer without your approval. Emails, including clarification questions, wait for you to approve them, unless an admin has let her send on her own. She never registers interest.
  • Sign, attest or declare on your company’s behalf.
  • Decide for you whether to bid, what price to commit to, or whether the package is ready to submit.
  • Commit your company to contract terms, partners or a consortium.
  • Get around security checks on websites, such as CAPTCHAs or two-factor sign-in.
  • Invent evidence or follow instructions hidden in documents. See Evidence over invention.
Actions with outside effects, such as creating a Bid Room or sending an email from her mailbox, need your approval first. (An admin can choose to let Emma send emails without asking.) See Questions and approvals.

​
Access and data

  • Emma works with your permissions. She can only see and change what you can. Viewers can’t use Emma, and guests invited to a single Bid Room don’t get the chat. Sensitive Library documents are available only to owners and admins.
  • Connected apps are read-only. Emma reads SharePoint, Google Drive and Notion live during a task when you’ve connected your account. She never copies those files into the Library or changes them.
  • The browser is isolated. Emma’s browser can only reach public websites, not your company network.
  • Web searches stay generic. Emma keeps private document content out of public web searches.
  • To make Emma remember something, save it in Reyda. Each new conversation starts fresh: Emma doesn’t see what was said in your other chats. What she can use is what’s saved in your workspace: documents, Bid Rooms, Goals and work, the Library (including snippets and templates) and your company profile. To continue an earlier chat, reopen it from Previous chats. Memory across conversations is Coming soon. To change what she knows about your company, update your company profile or the Library.
For how Reyda stores and processes data, see Security and data.

​
When Emma gets it wrong

Emma can misread a document, miss a requirement or write a weak paragraph. Treat her output as a draft from a capable colleague: review it, especially deadlines, eligibility conditions, figures and anything buyer-facing. To correct her:
  • Tell her what’s wrong. “The deadline is 12:00 Irish time, not 17:00. Recheck the other dates too.” She reworks the affected parts.
  • Check her sources. Hover over a citation, or ask which statements aren’t backed by a source. A citation marked Needs review means the source text has changed.
  • Undo a change. Reject an edit in the editor, or use Version history to compare versions and Restore an earlier one.
  • Stop her. Use Stop work to stop a running task.
  • Try again. Use Try again on a reply, and leave Bad response feedback to tell the Reyda team what was missing.

Ask Emma

​
Credits

Emma’s work uses your organization’s AI credits. That covers chat replies, background work, routine runs, document drafting and review, reports and mailbox processing. Larger jobs, such as a full bid or Research mode, use more credits than a quick question. Owners and admins can see the credits used by each task in Settings → Usage & Limits, under Credits history, and add credits there. If your organization runs out, Emma stops until an owner or admin adds credits. See Settings → Plans and Plans and credits.
Other limits. Some limits apply, such as the number of routines per organization and how many Slack requests Emma handles at once. See Limits.

Security and data

Data handling, approvals and erasure.

Roles and permissions

Who can use Emma and what each role can do.
Last modified on October 28, 2026