Mastering Epic One Configuration: Settings, Environments, and Admin Controls

A new hire's second day usually goes like this: sign in, look for the one setting that matters right now, get it wrong, ask someone. Multiply that by every person on a shop floor getting Epic One for the first time, and "configuration" turns into a real question, not a footnote. Not because the settings are complicated, there are only a handful, but because nobody wrote down which ones you actually touch versus which ones exist for the one admin who manages the whole company. This post is that answer: what's in Settings, what's in the admin console, and who's supposed to be looking at each.

Environments come first, because nothing else works without one

Before Epic One can answer a question about a real job, it needs an ERP environment to read from, and that's the first thing worth getting right. Settings holds your company's environment list plus your own personal Epicor login, and each environment gets a color: Live defaults to red, Pilot to amber, both changeable if that scheme doesn't match how your shop already thinks about it. That color isn't decoration. It drives the chip and badge in the chat header, so at a glance you know whether the answer you're about to get, or the change you're about to approve, is happening against your real production data or a sandbox. Adding an Epicor environment also unlocks Epicor mood, and it supports whatever your IT already uses to authenticate: API key, OAuth, Epicor Identity, or classic username and password. Running E2 JobBoss² instead, or alongside it? Site credentials is the same idea for that and other connected sites, with a test-connection button so you find out immediately if a login is wrong instead of discovering it mid-quote.

The rest of Settings is personal, not structural

Everything else in Settings is the stuff that makes Epic One feel like yours instead of a shared terminal. Avatar and voice lets you pick a character, or set it to None if you'd rather not have one at all, position it, and choose a text-to-speech voice. Mood switches between the six moods depending on what you're working on. Company Dropbox connects an account for document delivery, so generated documents land somewhere your team already checks. Notifications toggles SMS and email on or off. Profile is name, email, and password, the same three fields as any account settings page anywhere. None of this needs an admin, and none of it affects what a coworker sees when they sign in on the next desk. It's the difference between configuring the tool and configuring your seat at it.

What only an admin can touch, and why it's kept that way

The admin console lives at /admin, and it's the one part of configuration that isn't for everyone by design. User management there shows every person in the company grouped with online status, lets an admin edit user details, reset a forgotten password, toggle notifications on someone's behalf, or force-log a user out of their web session, mobile session, or both, useful the day someone leaves or a device goes missing. The other half of the admin console is document formats, and it works entirely in chat: drop one example of each document type into Dropbox under transcript-pipeline/templates, the filename naming the type, tell Epic One "learn my templates," and it replies with exactly what it learned. That's the whole process. It never happens on its own, and nobody without admin access can add or change a format, though everyone on the team can still generate documents using whatever formats are already learned.

None of this is configuration in the sense of a long implementation project. It's a short list of screens, most of which you set once and forget: connect your environment, confirm your credentials work, pick a mood if you care to, and let an admin handle the two things that touch everyone at once. If you're getting Epic One set up on your own ERP and want to walk through what your specific environment and credential setup looks like, the onboarding form is the fastest way to get that conversation started.