Office workspaces
The office interface organizes company work around an overview, an action stream and domain workspaces. Staff move between customers, opportunities, quotes, projects, execution and financial follow-up. A project supplies shared context without replacing the independent records and decisions in those workspaces.
Office entry requires the principal-staff surface condition. A subcontractor’s staff flag describes their own company and does not admit them to the principal’s backoffice. Capabilities further filter navigation and route content. The API and RLS remain responsible for actual resource authorization.
Workspace organization
Section titled “Workspace organization”| Navigation group | Inspected workspaces | Purpose and boundary |
|---|---|---|
| Arbetsyta | Översikt, Att göra, opportunities, mail, quotes, projects, work orders, planning, communication, document inbox and invoices | Coordinate customer work and review explicit decisions |
| Nätverk | Customers, subcontractors, UE jobs and UE review | Maintain relationships and procurement without merging customer and supplier authority |
| Ekonomi | Reports and cost basis | Interpret named datasets and allocate management costs |
| Mer | Time, people, articles, AI tools and feedback | Reach supporting functions according to their capabilities |
| Settings and privileged links | Company and integration settings; platform administration where admitted | Separate company configuration from platform authority |
The shared navigation configuration feeds desktop and mobile office navigation. A link can be absent from daily navigation while its route remains supported through a card or direct link. Conversely, an old link declaration is not proof that a route is admitted for every role. Frontend routes owns the entry and redirect map.
Overview and action stream
Section titled “Overview and action stream”Principal staff land on Översikt at /dashboard. The bell exposes the Att göra stream; the office also has an action-workspace entry. Action items represent decisions or reviews in owning business records rather than a second independent lifecycle. Resolving the underlying state removes the reason for that action.
An agent draft is one such review object. Staff can inspect and confirm the exact proposed version. Confirmation creates the supported native record; sending a quote and obtaining customer acceptance remain separate decisions. The AI proposal contract owns this distinction.
Customer mail and the document inbox are also separate. The mail workspace reads a bounded projection of the Estate archive. A document candidate needs human classification and business routing before it becomes an invoice or delivery-note input. Viewing an archived message does not send a reply or prove complete original coverage.
Moving between workspaces
Section titled “Moving between workspaces”A customer detail supplies relationships and company-local contact presentation. An opportunity can supply context for a quote. An accepted quote can authorize billing basis on a project. Planning allocates people and time; work orders carry execution instructions. Costs and reports then follow their own financial definitions.
The interface must preserve those distinctions when linking records. A source offer is not accepted authority. A calendar allocation is not a time report. A cost allocation is not supplier payment. Product purpose and the detailed workflows explain the connecting records.
Example: a decision that stays unresolved
Section titled “Example: a decision that stays unresolved”A synthetic office user opens a cost-review item, proposes a split between two projects and receives a revision conflict. The page retains the draft and asks for current source review. The queue item must not be treated as resolved merely because the editor displayed proposed values or the save request started.
Similarly, returning to the overview after creating an editable quote does not establish that it was sent. The owning quote state and delivery evidence determine what the next action can be.
Source and coverage limits
Section titled “Source and coverage limits”The route and navigation sources establish the inspected organization. Report permissions, historical date coverage and amount definitions belong to the Reports contract. Tests and shared receipts establish only their named layout or business scenarios. This article does not claim that every office task, dataset or role combination has received independent acceptance.