+995 574 856 856 WATG [email protected] 4600, Georgia, Kutaisi, Tamara Queen str, 12
NEW RSG 1.1.0 — Revit Server 2027 support and the new offline scenario
License API · 99.98% docs.rs-systems.org
RS Systems
RS Systems BIM Explosion
Войти
Products / Revit Server Guard / Documentation
RSG documentation · Interface guide

Revit Server Guard interface reference.

The documentation page has been rebuilt around annotated RSG interface screens. Each callout number is described in the table below the corresponding screen; only the table for the active site language is rendered.

10annotated screens
184numbered elements
22site languages
Solution overview

00What Revit Server Guard is and why it is needed.

Revit Server Guard is an administrative and security layer for organizations that continue to use Autodesk Revit Server and need controlled, auditable, role-based access to BIM data stored on their own infrastructure.

The problem it solves

Standard Revit Server is effective for shared model collaboration, but it does not provide deep administration, granular permissions, discipline-level write control, trusted workstation binding, or a complete operational audit. In practice, BIM teams often rely on informal rules and manual supervision, which creates risks of accidental overwrites, unauthorized synchronization and loss of accountability.

Purpose of RSG

RSG converts Revit Server from a largely opaque file-collaboration service into a managed access-control environment. It formalizes who may read, write, synchronize, administer, back up and monitor specific project areas, while giving BIM managers and IT administrators one control panel for users, roles, projects, disciplines and server versions.

How the system works

The solution combines the RSG Admin Panel, a .NET API service, local SQLite configuration databases and the RSG.NetTcpProxy gateway. Because Revit Server synchronizes through net.tcp traffic, the proxy is placed between Revit clients and the real Revit Server endpoint. It reads request metadata, identifies the user, workstation and target model, checks the current policy and only then forwards the approved request.

Access model

Instead of granting access only to an entire project, RSG binds project folders to documentation sections and disciplines. Roles can then receive read-only or read/write permissions for specific areas such as architecture, structures, MEP, life safety, shop drawings or local company standards. This protects adjacent disciplines from accidental modification and makes responsibility explicit.

1. Revit user requestA user opens, reads or synchronizes a central model through the configured RSG gateway address.
2. Proxy inspectionThe net.tcp proxy inspects SOAP metadata and resolves the Revit login, machine, IP address, project, folder and server version.
3. Policy decisionThe API checks user status, trusted binding, role matrix, discipline bindings and license coverage.
4. Allow, block and logApproved traffic is forwarded to Revit Server; denied or suspicious operations are blocked and written to the audit log.

Main functional areas

  • Users: trusted identity registry with login, workstation, IP, license state and connection history.
  • Projects: synchronization with the real Revit Server catalogue, project folder structure and section bindings.
  • Roles: visual permission matrix for read and read/write access across disciplines and stages.
  • RS Servers: gateway configuration, protected Revit Server versions, port routing and proxy telemetry.
  • Backups: scheduled project backup management with status monitoring for Revit Server data.
  • Audit and statistics: live event stream, PDF/XLSX export and activity analytics for managers and security teams.

The practical result is lower operational risk, clearer responsibility between disciplines, faster incident investigation and a safer on-premise BIM environment for organizations that cannot or do not want to move project data to an external cloud.

How to read this page

00Numbered interface documentation instead of decorative illustrations.

All previous decorative images on this documentation page were removed. The new content focuses on the actual RSG Admin Panel: navigation, catalogues, permission matrices, Revit Server gateways, backups, audit, statistics and configuration.

Each image is followed by a compact two-column table: the callout number and the description of the corresponding interface element. The JavaScript renderer selects the current locale and inserts only one language version into the page.

01 Interface screen

01Dashboard

Overview dashboard and global navigation

Callouts 1—18
Dashboard annotated interface
No.Element description
02 Interface screen

02Users

User registry, access summary and role assignment panels

Callouts 19—34
Users annotated interface
No.Element description
03 Interface screen

03Projects

Project catalogue, folder structure, section bindings and user access

Callouts 35—54
Projects annotated interface
No.Element description
04 Interface screen

04Roles

Role matrix for read/read-write permissions across disciplines and stages

Callouts 55—70
Roles annotated interface
No.Element description
05 Interface screen

05Disciplines

Discipline catalogue, project structure mapping and access roster

Callouts 71—86
Disciplines annotated interface
No.Element description
06 Interface screen

06RS Servers

Gateway, proxy and Revit Server protection matrix controls

Callouts 87—100
RS Servers annotated interface
No.Element description
07 Interface screen

07Backups

Backup jobs, schedules, destinations and backup telemetry

Callouts 101—116
Backups annotated interface
No.Element description
08 Interface screen

08Audit Log

Audit filtering, action history and event search controls

Callouts 117—130
Audit Log annotated interface
No.Element description
09 Interface screen

09Statistics

Activity analytics, KPIs and distribution panels

Callouts 131—144
Statistics annotated interface
No.Element description
10 Interface screen

10Configuration

System configuration, license controls, paths, branding and account security

Callouts 145—184
Configuration annotated interface
No.Element description
Next step Pricing →