Workspace Setup
Set ownership, team access, billing state, and operating responsibilities.
Workspace Setup
Use this page when you create a workspace, take over ownership, or prepare a team handoff.
This is the Workspace Administration entry for operators using Console and the Admin Panel. For app implementation, start with Quickstart and the domain task guides. Completing a P0 task guide proves that app task; launch still requires the operating checks on Launch Readiness.
Before changing anything, confirm the active workspace in Console. A role in one workspace grants no access to another; a workspace name, cookie, or header does not grant membership.
Setup Steps
Confirm workspace identity
Use a clear workspace name, confirm the owner, and keep the purpose short enough that future admins understand why the workspace exists.
Assign admin access
Add the first tenant-admin users, remove temporary access, and keep at least two trusted admins before launch.
Check billing state
Confirm the active plan and whether any subscription state needs attention before customer-facing work begins.
For usage-based billing, a newly derived charge of KRW 1–99 is exempted to zero. The invoice retains the calculated breakdown. Invoices already notified are not automatically changed.
For Enterprise usage billing registration, calculation, and invoices, see Enterprise usage billing below.
Record operating owners
Name who owns content, commerce, support, moderation, billing, and integrations before teams begin daily work.
Branding
Enter your logos and business details in Console under Settings → Site & Branding → Branding · SEO · Business. They are used in these places:
| Place | Values used |
|---|---|
| Top of the Console sidebar | Logo (or the logomark when there is no logo) and the dark mode logo |
| Customer notification email (orders, shipping, returns, events) | Logo, business name, and the business details you entered. A blank sender display name sends under the workspace name. |
| Customer sign-in code and password reset email | Logo and business name |
| Customer sign-in page (hosted sign-in) | The OAuth client's logo URL; when blank, the workspace logo and dark mode logo |
The business name comes from the business details, then the site title, then the workspace name. Email does not show SVG logos, and the customer sign-in page shows only logos on the 01 SOFTWARE media CDN.
Operator screens before a workspace is chosen, such as Console sign-in, password reset, and MFA, show 01 SOFTWARE. The customer sign-in page follows the customer's language preference and shows Korean or English.
Enterprise usage billing
Enterprise is not a self-service plan. It is usage-based billing calculated from a contract rate card for each workspace. To start, contact sales at software@01.works.
Review contract terms and register a card
- After sales activates a rate card for your workspace, they send a contract-terms link that opens the 01.software subscribe page.
- Sign in as a tenant-admin of that workspace and open the link. The page shows the contract rate card name, base fee, monthly minimum charge, effective period, charge at card registration, pre-charge notice period, and each meter's unit price, bucket, and included allowance.
- Review the terms, then register a card. The charge at registration is KRW 0, and registering a card does not charge you.
If the page says the terms cannot be verified, ask sales whether the link is current. If the terms change during registration, registration does not proceed and the latest terms are shown again; review them and register again. The effective period shows the dates recorded on the contract rate card; any price change or price hold across periods follows your contract.
How charges are calculated
Charges are calculated per calendar month in Korea Standard Time (KST).
| Item | Meaning |
|---|---|
| Base fee | Fixed monthly amount |
| Monthly minimum charge | If base fee plus usage overage is lower than this amount, the difference is added as the floor adjustment |
| Bucket | Counting unit for usage. Usage is divided by the bucket size and rounded up |
| Included allowance | Number of buckets included at no extra charge, not raw usage |
| Unit price | KRW amount per bucket above the included allowance |
billable units per meter = max(0, ceil(usage ÷ bucket size) − included allowance)
meter amount = billable units × unit price
subtotal = base fee + sum of meter amounts
amount before adjustments and exemption = max(subtotal, monthly minimum charge)When service starts or ends mid-month, the base fee and monthly minimum charge are prorated. Service days are the time from service start to end within that month, rounded up to whole 24-hour periods; they are not a count of calendar dates touched. Each amount is multiplied by service days ÷ days in the month and rounded up to the next KRW.
The finalized invoice total is the amount before adjustments and exemption plus any adjustment recorded before the notice (floored at KRW 0); if that result is KRW 1–99, the exemption described in the billing state step above applies. See Check the estimate and finalized invoices.
The following values are a hypothetical example of the calculation, not actual contract prices or defaults. With usage of 25,001, a bucket of 10,000, an included allowance of 1 bucket, and KRW 100 per bucket, ceil(25,001 ÷ 10,000) = 3 buckets minus the 1 included bucket gives 2 billable units and a meter amount of KRW 200. An included allowance of 1 means one 10,000-unit bucket, not 1 unit of usage.
The rate card has the following six meters, which use the usage snapshot of the closed month.
| Name on screen | Usage |
|---|---|
| API calls | Number of API calls |
| AI generations | Number of AI generations |
| Video delivery minutes | Video delivery time in minutes |
| Storage GB (last successful sample) | Last successfully sampled storage, converted to GB (10⁹ bytes) |
| Notifications | Number of notification emails |
| Documents (last successful sample) | Last successfully sampled document count |
Storage and documents use the last successful sample taken while that month was current. A decrease during the month is reflected in the next successful sample; a failed sample refresh preserves the previous successful sample. They are not a monthly average, a peak, or a value accumulated over time. Check the per-meter breakdown on the finalized invoice for the quantities actually billed.
Check the estimate and finalized invoices
A tenant-admin opens the workspace from the 01.software dashboard and uses the Billing tab to check:
- Current usage estimate: a non-final amount calculated from usage recorded so far in the current month and the active rate card. The finalized invoice may differ.
- Usage invoices: finalized invoices for closed months. Each shows status (Finalized, Charged, Failed), total, base fee, usage overage, floor adjustment, notice date, charged date, and a per-meter breakdown (usage, bucket, included, billable units × unit price = amount).
An invoice total can reflect the KRW 1–99 exemption or an adjustment recorded before the notice, so it can differ from the sum of base fee, usage overage, and floor adjustment. A finalized invoice is not changed by later rate card edits or usage recounts.
Settlement and charge timing
- A month's usage becomes a finalized invoice in scheduled processing after the settlement period through the 5th of the next month (KST). The invoice creation date is not fixed.
- When an invoice is finalized, an email notice of the finalized amount is sent to the workspace tenant-admins. The notice date is recorded once at least one email is sent; delivery to every recipient is not guaranteed, so check the notice date in the Billing tab.
- Charging is attempted in scheduled processing at least 7 days after the notice date. The exact charge date is not fixed; check the charged date for when payment was taken. A KRW 0 invoice is marked charged without a card payment.
- If the card is declined, the invoice shows as failed. Check the status in the Billing tab and contact software@01.works.
Billing questions and refunds
Send questions about invoice amounts or refunds to software@01.works. Refund requests follow the refund policy. This page does not promise separate eligibility conditions, processing times, or a self-service refund screen for usage invoices.
Platform super-admin operators review and approve billing-error corrections in the Admin Panel.
Workspace administrators do not receive an execution permission or a selfservice refund screen.
An unclear provider result stays under review and cannot be resent. A correction preserves the
original invoice, subscription and service access, and does not resume new Enterprise billing.
Operating rhythm
- Weekly, a tenant-admin reviews access, content queues, failed webhooks, and readiness blockers.
- Monthly, the workspace owner reviews plan, billing, quotas, keys, and unused features.
- During an incident, the workspace owner pauses launch or customer exposure when billing, keys, CORS, commerce, or moderation is blocked.
Access Roles
The exact operator roles are listed below. super-admin is a platform role; the other three are assigned per workspace. Customer accounts are separate from operator accounts.
| Role | Responsibility | Boundary |
|---|---|---|
super-admin | Platform administration and support | Global authority; select the target workspace for workspace operations |
tenant-admin | Workspace settings, features, keys, billing, and team access | Only workspaces where this role is assigned |
tenant-editor | Permitted content and commerce work | Collection-specific writes; no workspace settings, keys, billing, or membership administration |
tenant-viewer | Permitted review and reporting | Read-only; no operational writes |
The workspace owner is an ownership relationship, not a fifth role. Ownership controls transfer and deletion; ordinary administration still checks the operator's workspace role. Use individual logins and review access per workspace.
Handoff Checklist
- workspace owner is current
- at least two trusted admins exist
- temporary access is removed
- billing state is clear
- enabled feature owners are named
- launch support and moderation owners are named
Do not hand Secret Key ownership to a person or vendor before access, CORS, and operating owners are confirmed.
Next Actions
- Choose enabled areas in Feature Planning.
- Review credentials in Integrations & Keys.
- Run the final check in Launch Readiness.