Administration and preferences

Manage identity, organization context, preferences, and connections

Settings separates account-owned identity, organization context, personal interface choices, notifications, navigation, and developer data connections.

10 minute guide All users; Developer settings are for administrators and engineers

After this guide

You can tell which settings belong to the account, organization, device, or API connection and change them in the correct place.

Open Settings

1 Account
2 Organization
3 Preferences
4 Navigation
5 Developer

1. Review account and security

The account is the authentication boundary and contains the user who belongs to the organization.

1
Open Profile
Review the account ID, user identity, email, organization role, organization, workshop count, store count, and identity provider.
Open Profile
2
Understand the hierarchy
One account contains the user. The user belongs to an organization. The organization owns many workshops and stores.
3
Review Security
See authentication ownership, two-step verification state, last sign-in, and active sessions.
Open Security
4
Use the identity provider for credentials
Passwords, recovery, two-step verification, and session revocation are managed by the configured identity provider rather than stored by MakerDesk.

2. Review organization context and regional display

General settings show shared operating context while keeping display defaults explicit.

1
Confirm the organization
Review the organization name and its workshop and store collections.
Open Organization
2
Confirm the active workshop
The active workshop controls which local operations appear elsewhere in the app.
3
Set time zone and format
Choose the time zone and 12- or 24-hour format used to present due dates and operational timestamps.
4
Set the measurement system
Choose imperial or metric display. Material records still retain their explicit consumption units.

3. Set personal preferences

Appearance, notifications, and navigation shape the current user experience without rewriting operational records.

1
Choose appearance
Select light, dark, or system color mode; choose the MakerDesk accent; and reduce motion when needed.
Open Appearance
2
Choose operational notifications
Control alerts for new orders, build blockers, low stock, and the daily summary.
Open Notifications
3
Show or hide planned routes
Planned routes explain the intended product shape but may add visual noise. Toggle them in Navigation settings.
Open Navigation
4
Choose the contextual sidebar default
Start area sidebars expanded for discoverability or collapsed for more working space.

4. Configure the data connection

Developer settings own environment connection choices, not normal workshop operations.

1
Choose Mock or API
Mock uses local API-shaped fixtures for UI development. API connects MakerDesk to the configured backend.
Open Developer
2
Enter the API base URL
Use the environment-specific backend URL. Do not place connection values in route files or UI-only data.
3
Test the connection
Confirm reachability, response status, version, latency, and the time of the last check.
4
Match the version
Use the reported API version when diagnosing contract differences between frontend expectations and backend responses.

Ownership stays explicit

Account identity, organization operations, personal UI preferences, and developer connections are separate settings concerns.

Mock data follows API shape

Anything expected from the backend belongs in mocks and shared data types. Static help and interface choices belong in data.

Getting started

Learn the navigation, establish the minimum catalog and inventory records, then turn customer demand into an operational decision.

Open Profile

Understand the hierarchy

Review Security

Use the identity provider for credentials

Confirm the organization

Confirm the active workshop

Set time zone and format

Set the measurement system

Choose appearance

Choose operational notifications

Show or hide planned routes

Choose the contextual sidebar default

Choose Mock or API

Enter the API base URL

Test the connection

Match the version

Ownership stays explicit

Mock data follows API shape

Continue learning