Answers for the person who has to sign this off.

Staged rollout and rollback

Each person is assigned to a channel — Production or Beta. A Beta release reaches only the people in Beta, so you can pilot a tool before everyone gets it.

The people who write tools ask for Production themselves, tool by tool, with a note on what they tested. An administrator tries the tools in Beta first — one click switches their own ribbon for the session — then approves or rejects each request, and only the tools in an approved request reach everyone — so one person’s finished tool never waits for, or drags along, anyone else’s.

Every release to Production keeps a copy of what was there before, so a bad release is undone in one action. Both are recorded in the audit trail with the administrator’s name.

Crash isolation and Safe Mode

If a tool fails, the user gets a plain-language message confirming their model is unaffected, and the failure is logged with full detail for you.

A tool that keeps failing is benched automatically: the button greys out with an explanation and refuses to run, and it comes back once it behaves. A one-off glitch doesn’t bench a tool permanently.

• Holding Shift while Revit or AutoCAD starts loads core only, and offers to reset benched tools
• Failure counts are visible to administrators, so you fix the tool that’s actually failing

Role-based access

Assign roles to Windows users or Active Directory groups, and decide which roles get which tools. People without the role never get the tool at all — it isn’t just hidden from the ribbon.

Access keeps working when the shared drive is unreachable. Roles are optional: without them, everyone gets every published tool.

Several teams, one firm

A firm that works as several teams can give each one its own tabs, its own tool-makers and its own leaders. A team’s members publish into their team’s tabs and ask for Production, and the team’s leaders approve, retire or undo those tools — no other team can.

Work in progress stays inside the team. Released tools don’t: anyone can add another team’s released tabs from the Tool Store and use them, without being able to change them. IT sets the teams up once, by name or Active Directory group.

Revocation — the kill switch

When a tool has to stop being used immediately, withdraw it centrally. On the next sync it greys out on every machine, with your reason shown to anyone who clicks it.

The kill switch is protected so that only your administrators can use it, and it is switched on while we help you secure your deployment during setup.

Audit trail

Governance actions — promotion, rollback, revocation, approval, rejection — are recorded in a tamper-evident log: if an entry is edited or deleted, verification shows it, and if the whole log is rewritten or cut short, every computer that saw it reports it. Each entry can also be collected from the Windows Event Log, out of users’ reach.

It records when, who and what. It is designed to answer “who changed what, and when” months later, in front of someone who is not inclined to take your word for it.

Two-person approval

Optional. When enabled, promoting to Production becomes a request: an administrator files it with a reason, and a different administrator approves it. Yugmir refuses self-approval outright. Requests, approvals and rejections all land in the audit trail.

Off by default — firms that don’t need separation of duty aren’t slowed down by it.

Tool integrity

Yugmir can check the tools your firm publishes before they load, so a tool that has been changed without authorisation is detected. Administrators decide how strictly it is applied.

Telemetry and privacy

Usage data never comes to us. It is kept on your own file server, and the reporting in the product reads it from there. We have no access to it.

Consent is two-layered:

• The firm can set collection to optional, required or disabled for everyone
• Where the firm leaves it open, each user is asked once, and can change their choice later from the ribbon
• Disabled always wins. If the firm switches collection off, no user setting can turn it back on

What’s recorded is operational: which tool ran, whether it succeeded, when, on which Revit or AutoCAD version, for which user. No model content and no drawing data.

Licensing that survives a bad connection

Yugmir needs the internet once, to activate. After that it keeps working through an offline grace period — so a site office on a poor line, or an engineer away from the network, doesn’t lose their tools because a licence server was unreachable.

Everything is installed locally. There is no dependency on our servers for day-to-day work.

Common questions