How Struxen is organized

Struxen has two containers and four products. The containers are your organization and its projects. The products are Core, LEDGER, STRUX and VANTAGE, and all four operate on whichever project you currently have open.

Read this page once and the rest of the documentation will tell you where you are.

Organizations

An organization is your company. It owns billing, the people, the vendor directory, the cost-code structure and every project.

• Everyone you work with in Struxen is a member of one organization.
• Organization roles are Owner, Admin and Member. See Roles and permissions.
• Credits, invoices and the payment method are organization-level. See Billing.
• Joining is by invitation from an Owner or Admin. There is no self-service sign-up.

If your company already uses Struxen, ask an Owner or Admin to invite you. Creating a second organization gives you a second account and no access to your colleagues' work.

Projects

A project is one job. Drawings, specifications, RFIs, submittals, daily logs, findings, budgets and AI runs all live inside a project and are scoped to it.

CORE is free for up to 3 projects, with no organization fee. Creating a CORE project inside that tier is not a purchase. See Projects for the full flow.

One project at a time

Struxen uses a current project model. You pick a project in the switcher and every surface in the app re-scopes to it: the registers, the documents, the assistant, the settings under Current project. Switching projects reloads all of it.

There is no per-project URL to bookmark. /overview is always the home of whichever project is current, and there is no separate per-project dashboard route. Your selection is remembered in the browser you made it in, so a second browser or a new device starts from the first project in your list.

The project switcher sits in the top bar and is labelled with the project you have open. To see every project at once, open the switcher and choose All projects. That view is described in Projects.

The four products

The left rail carries Overview first, then one row per product, then the two surfaces that are shared across products.

Product	Where	What it is
Struxen Core	/core	Run the project. The registers and field modules: drawings, documents, specifications, submittals, RFIs, observations, schedule, daily logs, punch, meetings, inspections, safety, photos, transmittals, team.
Struxen LEDGER	/ledger	Run the money. The prime contract, commitments, the change chain, direct costs and the budget.
STRUX	/strux	Ask the drawing set. Cited question and answer over your project documents, plus the purpose-built instruments.
Struxen VANTAGE	/vantage	See what was drawn. Automated multi-document quality-control runs, and the 3D read of the drawing set.

Opening a product row swaps the right-hand module rail to that product's modules. The rail stays mounted while you move around inside the product, so you never lose your place in Core by opening a register.

Two surfaces belong to no single product and sit below the product rows:

• Findings collects what the automated checks turned up, from every producer that contributed. See Findings.
• Reports is where exports and canned reports live. See Reports.

What each product costs

CORE is free for up to 3 projects, with no organization fee. LEDGER, STRUX, and VANTAGE are paid. They are not in the CORE free tier and they are not bundled into the $500/month organization fee that starts above that tier, or when you add a paid product. VANTAGE is $250 per month per project, enabled per project rather than per organization. Billing has the full picture.

Where settings live

Settings are grouped by what they belong to. Open Settings and the rail shows three groups.

Account management applies to the whole organization:

Section	Path
Organization	/settings/organization
Users & teams	/settings/users-teams
Roles & permissions	/settings/roles
Billing & subscription	/settings/billing
Vendors	/settings/vendors
Cost codes	/settings/cost-codes
WIP portfolio	/settings/wip-portfolio
Audit log	/settings/audit-log

Integrations holds one section, /settings/integrations, where you connect Autodesk. See Integrations.

Current project applies only to the project you have open, and its eleven sections are listed in Projects.

WIP portfolio reports every job in the company and is restricted to organization Owners and Admins.

Things that are true almost everywhere

A handful of rules cut across every module. They are repeated on the pages where they bite, but knowing them up front saves confusion.

Autodesk-linked projects behave differently from native ones. A project you created in Struxen writes to Struxen. A project linked to an Autodesk hub mirrors Autodesk, which is the source of truth: local edits do not push back, and a linked project refuses direct document uploads. See Integrations.

Demo projects are read only. Every write control is disabled on them.

Permissions are per tool. Most modules resolve to one of four levels for you: None, Read only, Standard or Admin. A few modules do not have a permission key of their own and inherit a neighbouring one, which Roles and permissions sets out. When an action needs a level you do not have, the control says so rather than failing silently.

AI work costs credits, reading does not. Asking STRUX, running a VANTAGE check and indexing an uploaded document all draw on the project's credit balance. Browsing registers, opening documents and non-AI editing do not. A project at zero credits stays fully readable and stops accepting AI work.

Base-plan accounts get no AI indexing. On a Core-only plan, documents still upload, store, version and download normally. They land with the status Not processed and are not searchable by STRUX.

Where to go next

• Getting started walks the first hour end to end.
• Projects covers creating, configuring and deleting a project.
• Project home covers the widget board at /overview.
• Struxen Core covers the /core landing surface.