Quickstart: your organization

Everything on this page happens in a browser. You do not need to be an engineer to finish it, and nothing here requires anyone to write a line of configuration.

By the end, Memnox will be reading two of your systems, will have proposed a decision it believes your team made, and you will have approved or rejected it.

1. Sign in

Open the console and sign in with Google. There is no password, by design: a credential nobody can lose is a credential nobody can leak.

What happens next depends on how your instance is configured:

• Your email is already provisioned. You land in your organization with the role an admin gave you.
• Nobody has heard of you, and self-service is on. You get a new organization of your own, never membership of somebody else's.
• Nobody has heard of you, and self-service is off. You are refused, and an admin has to add you first. See Roles and access.

2. Finish onboarding

The first time in, Memnox asks for the company name, what it does, and who you are. This is not decoration: the extraction step later uses it to tell a decision about your product from a decision about someone else's. An empty profile is the usual reason suggestions come back about other companies.

3. Connect your first two systems

Go to Connectors. Start with one system where the conversation happens (Slack, for example) and one where the work happens (GitHub, Jira, Linear). One alone is not enough to show what Memnox is for.

1. 1

   Pick a toolkit

   Search the directory. There are 500+ of them and they all behave the same way, because none of them has code of its own here.

2. 2

   Approve the consent screen

   You will be asked to allow access, in the tool's own words. Whose name appears on that screen depends on whether your admin registered your own OAuth app, see Your own OAuth app.

3. 3

   Choose what it listens to

   A connection on its own is quiet. Subscribing to a trigger is what makes events start arriving. See Triggers and events.

4. Watch events arrive

Open Activity. Within a minute or two of somebody sending a message or merging a pull request, it should appear.

5. Let Memnox propose a decision

Memnox reads the events and proposes candidate decisions, things it believes your organization has decided and would want held to in future.

Run extraction from the Decisions screen. This is the one step in the whole product that uses an LLM, and its output is a suggestion and nothing else.

6. Approve or reject it

This is the moment the product turns on. Approving records the decision, stamped with your name as the reviewer, and sends it to the runtime where it becomes a constraint agents are checked against.

Rejecting costs nothing. A rejected suggestion teaches Memnox what your organization does not consider a decision.

7. Invite the people who will use it

Go to Settings → Members. Three roles, and the difference between them is what they may change, not what they may see.

What to do next