Setting up EOS

About twenty minutes, and nothing to install on a server. Nerio reads; it does not deploy into your stack.

Step 1. Sign in and open the workspace

Use the account your organization's owner added you with. The workspace is keyed to your organization. You will see it empty, which is correct: nothing is connected yet.

Step 2. Connect the first system, read only

Pick the system whose numbers are argued about most, usually the ERP. EOS asks for read only credentials, or a read only service account, and it will refuse a credential that carries write scope. If your system offers a reporting replica, use it.

Step 3. Connect the second system

One system alone cannot disagree with anything. The second connector is where EOS starts to earn its keep. Procurement and contracts are the usual pair with an ERP.

Step 4. Name the people who decide

For each domain you connect, name the person who has authority to settle a contested figure. EOS routes to a person, never to a queue, and a finding with no named authority is not routed at all.

Step 5. Watch one week

Do nothing else. At the end of the week you will have a list of contested figures with evidence chains. Work one of them the way you would have anyway, and compare the time it took.

What good looks like after a week

Between three and thirty contested figures for two connectors, most of them small, at least one that surprises someone. If you see none, the two systems agree or the connector is scoped too narrowly; write and we will look at the scope with you.

What to do if a connector will not connect

The failure text names the reason and the scope it asked for. The three usual causes are a credential with write scope, an allow list that does not include our egress, and a replica that lags far enough that the two systems always disagree. All three are fixable in the connector settings.