Task-shaped instructions for the DigiFX Media Console: getting an account, finding the surface that does the job, and understanding what a given action costs before you run it.
01Getting in
Two doors lead into the Console, and they are not interchangeable.
Onboarding starts at the onboard page, which asks for an access code before it will unlock the Console and walk you through setup. If you have been given a code by DigiFX, that is the door to use.
Direct sign-in uses either a Google account or an email address and password, both handled by Google Firebase Authentication. If you forget your password, the forgot-password route sends a reset through the provider. If you lose the authenticator app holding your second factor, that is a different problem with a different door — password reset does not clear a second factor.
A verification email goes out when an account is created, and the account works immediately rather than waiting on it. Verification does gate one thing specifically: you cannot enroll two-factor authentication until your address is verified.
02Where the work happens
The Console is not one screen. A how-to guide will usually name a route, so it helps to know what each one is for.
- Hub and Dashboard are the operational overviews — what is active, what changed, what needs attention.
- Create is the canvas editor: layers, selections, adjustments, export.
- Studio is the audio session surface. Motion handles motion projects, Stream handles broadcast, Social handles content and channels, and Agency handles campaign work.
- Library holds your assets. Projects is the different thing next to it: a single list of your saved sessions across every live creative tool, so you can reopen work without first remembering which tool made it.
- Settings holds account and preference controls, including the security section where two-factor enrollment lives.
- Security reports real account state — connection, email verification, enrolled factors, a live data-layer round-trip, and a merged log of account events.
03What costs credits
Metered actions are the ones that call an outside service or move real bytes: AI calls, image generation, live-stream minutes, and storage bandwidth. Each one writes a usage record against your account, so both you and DigiFX can see what credits were spent on rather than arguing about it later.
Credits are bought through Stripe, and receipts are emailed. The practical habit worth forming: before running a long or repeated generative operation, check your balance and your recent usage, because a metered action that fails part-way still consumed whatever it consumed.
04How to read a guide on this site
Each how-to names the route it applies to, states what must already be true before you start, and describes what success looks like at the end. Where a capability is not yet available, the guide says so rather than describing a button that does not exist.