RSG Admin Panel
Description interface, solution and instruktsii by vnedreniyu
RSG solution overview
RSG (Revit Server Guard) is an administrative module for Revit Server 2021/2022/2023/2024/2025/2026/2027. Its purpose is to bring access management, audit, project maintenance and RS gateway control from scattered server settings into a single web-based admin panel.
The solution addresses Revit Server’s main organizational risk: without a separate control layer, permissions at the project, role and section level cannot effectively be assigned and verified centrally. RSG introduces a formal model — user → project → role → section/folder — while the proxy layer turns this model into actual permission or denial of Revit client operations.
key tasks
- sozdat edinyy reestr users, projectov, roley and razdelov;
- svyazat realnye papki Revit Server with distsiplinami/razdelami documentation;
- naznachat projectnyy access and sektsionnye rights without manual editing konfiguratsionnykh files;
- zaschischat Revit Server via proxy, which propuskaet only razreshyonnye operations;
- View the action audit: who changed or attempted what, and when.
- Configure backups centrally and receive activity reports.
- podderzhivat neskolko versiy Revit Server and raznye circuits/strany in one paneli.
solution components
Komponent | Rol | Chto dayot |
RSG Admin Panel | React/Vite-interface administratora. | Navigation, tables, role matrices, forms, localization, theme and reports. |
RSG.API | . NET 8 backend and Windows Service. | REST API, admin-panel authorization, SQLite, audit, reports, backups, proxy management and work with the RS catalog. |
RSG.Core | General suschnosti and kontrakty. | Users, projects, roles, sections, rights, litsenzirovanie, DTO and interfacey. |
RSG.Infrastructure | Realizatsiya servisov and access k dannym. | EF Core/SQLite, BackupService, ProjectService, RoleService, RevitProxyManagerService, LicenseService. |
RSG.HttpModule | Middleware on storone RSG. API. | Check access on REST-zaprosakh, filtratsiya vydachi katalogov, HTTP gateway/marshrutizatsiya. |
RSG.NetTcpProxy | .NET Framework 4.8.1 net.tcp proxy. | Perekhvat WCF/net.tcp trafika Revit Server, izvlechenie userya/machine/IP, blokirovka or propusk operatsiy. |
SQLite base | rsg.db and rsg-proxy.db. | Core permissions model, settings, license, log and proxy service data. |
How RSG solves its tasks
1. Inventory: RSG reads/refreshes the Revit Server catalog, groups projects by RS version and creates local project records.
2. Normalizatsiya struktury:Papki projecta svyazyvayutsya with razdelami: naprimer, AR/KR/OV/VK stanovyatsya upravlyaemymi distsiplinami, a ne prosto papkami.
3. Role model: a role receives section-level permissions. A user is assigned a role in a project; a project administrator receives extended permissions.
4. Primenenie politiki:HTTP middleware and net.tcp proxy proveryayut userya, project, put and tip operations. Chtenie/zapis prinimayutsya or otklonyayutsya by modeli RSG.
5. Audit and reporting: actions and denials are written to the log; statistics and exports provide evidence for reviewing access changes and activity.
6. Maintenance: backups, settings import/export, proxy diagnostics and the gateways page reduce dependence on manual server work.
Access logic
Uroven | Pravilo | Prakticheskiy smysl |
User | user ischetsya by Revit login, AD-identichnosti, machine and IP/doverennym bindingm. | One login dolzhen sootvetstvovat ponyatnomu subektu access. |
project | Zapis UserProjectAccess dayot vidimost projecta; rol «Net» zapreschaet access. | user vidit only naznachennye projects. |
Koren projecta | CanWriteProject razreshaet zapis in korne projecta, no ne automatically vnutri razdelov. | Service operations at the root can be allowed without granting full access to every discipline. |
Section/papka | SectionFolderBinding svyazyvaet papku with kodom section; RoleSectionAccess. CanWrite razreshaet zapis. | rights vydayutsya on distsipliny, a ne on proizvolnye ruchnye isklyucheniya. |
Administrator projecta | IsProjectAdmin or vstroennye admin-roles dayut polnyy access k projectu. | Needed for BIM-administratora/otvetstvennogo za project. |
RSG Admin | Administrator system prokhodit proverku with polnymi rightsmi management. | Rol for obsluzhivaniya samogo RSG and kriticheskikh nastroek. |
Feature description
Unified model access:Users, projects, roles and sections svyazany in one modeli. This luchshe, chem khranit logiku access in pamyati otdelnykh administratorov or in razroznennykh faylakh.
Sektsionnyy kontrol:RSG uchityvaet ne only project tselikom, no and papki/sections vnutri projecta. This osobenno vazhno for BIM-protsessov, gde raznye ispolniteli otvechayut za raznye distsipliny.
Proxy as enforcement-sloy:Panel ne prosto pokazyvaet tablitsy, a mozhet fizicheski blokirovat operations Revit Server via proxy-kontur.
Audit:Zhurnal fiksiruet changes and otkazy, chto snizhaet risk nerassleduemykh intsidentov.
Masshtabiruemost interface:Tablitsy, filtry, sortirovki, derevo, kartochki sostoyaniya and eksport pozvolyayut workt with bolshim chislom projectov/users.
Multiversionnost:Profili proxy and instansy RS rasschitany on Revit Server 2021-2027.
Servisnaya ekspluatatsiya:RSG. API ustanavlivaetsya as Windows Service, ispolzuet ProgramData for runtime-data, pishet logi and upravlyaet firewall for HTTP-porta paneli.
Lokalizatsiya and tema:Interface uzhe contains i18n-kontur, pereklyuchenie yazyka, strany and temy without perelaunch prilozheniya.
Installation, launch, and configuration guide
Below is a practical sequence for configuring RSG to work both as the management panel and as a protective proxy layer for Revit Server.
1. preliminary terms
- Windows Server with ustanovlennym Revit Server nuzhnykh versiy.
- . NET 8 Runtime/Hosting Bundle for RSG. API, if publikatsiya ne self-contained.
- . NET Framework 4.8.1 for RSG. NetTcpProxy.
- Node.js/npm nuzhny only on machine sborki frontenda, a ne obyazatelno on boevom servere.
- rights lokalnogo administratora for ustanovki Windows Service, openiya firewall and changes konfigov Revit Server.
- The ProgramData/RSG folders, backup directories and logs must be accessible to the service account.
- DNS-imya or staticheskiy IP server, which budut ispolzovat BIM-clients.
2. Initial configuration in UI
- Open «Konfiguratsiya» and check status base, license, putey and versions.
- Ustanovite or aktiviruyte litsenziyu RSG.
- Review/create users and configure their active status, roles, IP/machine binding or AD identity.
- Open “Projects”, refresh the RS catalog and import the required projects.
- Open «Sections» and nastroyte catalog distsiplin, if on otlichaetsya ot vstroennogo.
- Svyazhite papki projectov with razdelami via privyazki SectionFolderBinding.
- Open “Roles” and configure the permissions matrix by section.
- On the “Overview” page, verify the final assignment matrix.
Port and network circuit assignment
Kontur | By umolchaniyu | Gde zadayotsya | Kto dolzhen imet access | Kommentariy |
RSG Admin Panel / API | TCP 5080 HTTP | appsettings: RSG:Http:Port or --install --http-port | Only administratory RSG / BIM-adminy | The RSG.API service listens on this port. The installer opens the “RSG Admin Panel” firewall rule. |
Dev UI Vite | TCP 5173 | RSG.AdminPanel/vite.config.js | Only razrabotchik | Needed for razrabotki. In boevoy ekspluatatsii UI obychno sobran in RSG. API/wwwroot. |
Revit Server Admin HTTP | TCP 80 | Proxy shared settings: AdminPort; IIS/RS | RSG. API and administratory | Ispolzuetsya for RevitServerAdmin{year}/ and AdminRESTService diagnostics. |
Proxy public net.tcp | TCP 808 | Proxy shared settings: ListenPort | Revit-clients | Publichnyy sign in proxy. clients dolzhny idti syuda, a ne directly in Revit Server. |
Revit Server target net.tcp | TCP 8086 | Proxy shared settings: TargetPort; konfig RS | Only proxy and lokalnyy server | Internal endpoint of the actual RS. Direct user access should preferably be blocked. |
Decision API / sluzhebnyy kontur | http://127.0.0.1:5080/api/proxy-gateways/decision | Stroitsya from RSG:Http:Port or RSG:NetTcpProxy:DecisionApiUrl | Locally / sluzhebno | In kode RSG. API est endpoint decision; current NetTcpProxy takzhe chitaet rsg.db and rsg-proxy.db directly, poetomu DB-puti kritichny. |
Osnovnaya BD | C:\ProgramData\RSG\rsg.db | RSG:DatabasePath | RSG.API, proxy read-only | Khranit users, projects, roles, sections, license, flagi zaschity. |
Proxy BD | C:\ProgramData\RSG\rsg-proxy.db | RSG:NetTcpProxy:DatabasePath / ProxyDatabasePath | RSG. API and proxy | Khranit parameters listen/target and sluzhebnye sobytiya proxy. |
Logi RSG. API | C:\ProgramData\RSG\Logs\rsg-*.log | Serilog in appsettings | Administratory | Diagnostika backend and Windows Service. |
Logi proxy | C:\ProgramData\RSG\Logs\Proxy | RSG:NetTcpProxy:LogsPath / ProxyLogsPath | Administratory | Diagnostika launch, marshrutizatsii, neizvestnykh users and otkazov. |
Port selection rules
- Ne ispolzuyte 0-1023 for RSG:Http:Port; code otkatyvaet takie znacheniya on 5080.
- Ne naznachayte one and tot zhe port RSG. API, proxy listen and realnomu Revit Server.
- PublicHost must not be localhost/127.0.0.1 if clients connect from other machines.
- The proxy ListenPort must be reachable from Revit client workstations.
- TargetPort Revit Server dolzhen byt accessen proxy, no ne dolzhen byt udobnym obkhodnym marshrutom for obychnykh users.
- If TargetPort changes, verify the RS configuration changes and restart the related Revit Server/IIS services according to the local setup.
- If ispolzuetsya HTTPS/TLS for admin-paneli, postavte reverse proxy/IIS pered RSG. API and ogranichte pryamoy HTTP-access on 5080.
Why the proxy is needed and how to run it
The proxy is required because Revit Server handles Revit client operations not only through administrative REST, but also through WCF/net.tcp transport. The admin panel can store the permissions model, but by itself it does not intercept Revit traffic. The proxy becomes an intermediate layer between the client and the actual Revit Server: it accepts the net.tcp connection, identifies the user/machine/IP and operation path, checks them against the RSG model, and only then forwards the request.
What the proxy does
- slushaet publichnyy net.tcp port, obychno 808;
- Forwards allowed traffic to the actual Revit Server target host/port, usually 127.0.0.1:8086.
- izvlekaet identichnost from NBFX/SOAP/WCF messages and soketa klienta;
- Checks the RS-version protection flag: Protected_2021…Protected_2027.
- Controls visibility of project root folders according to the user’s assignments.
- Allows writing only to the project root, specific sections or the entire project according to the role.
- logiruet neizvestnykh users and spornye popytki access;
- Filters the Revit Server root listing so the user does not receive projects they should not see.
Step-by-step proxy launch
- Skopiruyte RSG. NetTcpProxy.exe and zavisimosti in catalog, ukazannyy in RSG:NetTcpProxy:BinaryPath, naprimer C:\Program Files\RSG\NetTcpProxy\. Open RSG Admin Panel → «Shlyuzy RS».
- In Shared settings zadayte PublicHost: DNS/IP, which budut ispolzovat Revit-clients. Ne ukazyvayte localhost, if clients ne on etom zhe servere.
- Zadayte ListenPort, naprimer 808. This port sign ina proxy for klientov.
- Set TargetHost to the actual Revit Server host. If the proxy is installed on the same server, this is usually 127.0.0.1.
- Set TargetPort to the internal Revit Server net.tcp port, usually 8086.
- Zadayte AdminPort: HTTP-port administrativnogo site Revit Server, obychno 80.
- Check puti ProxyExecutablePath, ProxyDatabasePath, RsgDatabasePath and ProxyLogsPath.
- Click «Primenit». RSG zapishet shared settings, proxy config and aktualnuyu access-policy.
- For the required RS versions, enable the profile and AuthorizationEnabled. Versions not covered by the license should remain disabled.
- Click «Detekt» for kazhdoy versions. Normalnaya diagnostika dolzhna videt Admin UI, serverProperties and contents.
- Click “Start”. After startup, verify the process status, PID, ListenPort availability and the tail of the log.
- Perenastroyte klientskie podklyucheniya Revit Server on PublicHost:ListenPort.
- Zakroyte pryamoy access users k TargetPort, inache proxy mozhno oboyti.
- Test with a test user: no assignment → denied; project role assigned → project visible; section permission assigned → writing allowed in the required section.
What RSG creates when launching the proxy
File/parametr | Purpose |
RSG.NetTcpProxy.exe.config | Runtime-konfig proxy: ListenAddress, PublicListenAddress, TargetAddress, puti BD/logov, timeout/cache parameters. |
access-policy.json | Snimok politiki for versiy RS and users: protectionEnabled, allowedProjects, writeFolders. |
rsg-proxy.db | Proxy service settings and the log of unrecognised/service events. |
RSG.NetTcpProxy.log | Podrobnyy log marshrutizatsii, oshibok porta, SQLite, rezhima bypass/protected and otkazov. |
GlobalSettings Protected_YYYY | Flag vklyucheniya zaschity for versions Revit Server. |
Important proxy security logic
- If version RS ne zaschischena, proxy mozhet workt in bypass-rezhime: trafik idyot dalshe, no zaschita fakticheski ne primenyaetsya.
- If license ne pokryvaet versiyu RS, policy-file ne dolzhen vklyuchat protectionEnabled for etoy versions.
- If proxy ne mozhet open rsg.db, on mozhet pereyti in rezhim dopuska/obkhoda, poetomu accessnost and rights on bazu kritichny.
- If u userya net doverennoy privyazki login+machine+IP, on mozhet popast in spisok neizvestnykh zaprosov. After proverki administratora takuyu privyazku mozhno prinyat.
- Nelzya ostavlyat vnutrenniy target-port RS openym for users, inache oni smogut obraschatsya k Revit Server minuya RSG.
Reglament settings access
Shag | Deystvie | Check rezultata |
1 | Sozdat/importirovat users. | In «Users» vidny aktivnye zapisi, IP/machine/AD zapolneny for realnykh klientov. |
2 | Refresh catalog RS. | In «projects» vidny instansy Revit Server and realnye papki. |
3 | Importirovat projects in RSG. | The project received an RSFolderPath and is displayed in the list. |
4 | Svyazat papki with razdelami. | In «Sections»/«projects» est privyazki FolderPath → SectionCode. |
5 | Nastroit roles. | CanWrite is enabled in the role matrix for the required sections. |
6 | Naznachit useryu rol in projecte. | In «overview» poyavilas svyazka user-project-rol. |
7 | Refresh/zapustit proxy. | access-policy.json aktualen, proxy running, ListenPort reachable. |
8 | Protestirovat Revit-klientom. | Razreshyonnye operations prokhodyat, zapreschyonnye vozvraschayut otkaz and popadayut in audit/log. |
Backup procedure
- Zadayte BackupBasePath in appsettings or in configurationkh projecta.
- For each project, specify the backup path and schedule on the “Backups” page.
- Verify that the RSG.API service has write permission to the backup directory.
- Run a manual backup before enabling the schedule for the first time.
- Check istoriyu: uspeshnyy status, vremya, put and otsutstvie oshibok.
- Otdelno kopiruyte C:\ProgramData\RSG\rsg.db, rsg-proxy.db and proxy-gateways.json as konfiguratsionnuyu chast RSG.
Diagnostics and typical issues
Simptom | Veroyatnaya prichina | Chto verify |
Panel ne opens | Sluzhba ne zapuschena, port zanyat, firewall. | sc query RSG.API, netstat -ano, firewall rule «RSG Admin Panel», RSG:Http:Port. |
Catalog RS ne chitaetsya | Nevernyy host/admin port/API path or RS neaccessen. | Auto-detect, URL RevitServerAdminRESTService{year}/AdminRESTService.svc/serverProperties. |
Proxy ne startuet | Ne nayden exe, zanyat ListenPort, net prav on BD/log. | Puti in «Shlyuzy RS», RSG. NetTcpProxy.log, netstat, rights ProgramData\RSG. |
clients ne podklyuchayutsya | PublicHost/ListenPort neaccessny or clients idut on staryy address. | DNS/IP, firewall on ListenPort, settings klienta Revit Server. |
Zaschita ne srabatyvaet | Version ne zaschischena, proxy in bypass, clients obkhodyat target-port. | Protected_YYYY, AuthorizationEnabled, status proxy, firewall on TargetPort. |
user ne raspoznan | Net login/machine/IP privyazki or Revit ne peredal zagolovki. | History podklyucheniy, unknown requests, Adopt/binding IP/machine. |
Otkaz when zapisi in section | Net SectionFolderBinding or u roles net CanWrite. | Section bindings, role matrix and user assignment within a project. |
Otchyoty/eksport ne formiruyutsya | Oshibka backend or prav on papku vremennykh files. | Logi RSG. API, rights sluzhby, state base. |
Production operation recommendations
- Immediately naznachit parol vstroennomu Administrator and ogranichit access k paneli only administratoram.
- Ispolzovat otdelnoe DNS-imya for RSG Admin Panel and otdelnoe DNS-imya/port for Revit proxy.
- Close pryamoy userskiy access k vnutrennemu target-portu Revit Server.
- Khranit rsg.db, rsg-proxy.db, proxy-gateways.json and appsettings.json in regulyarnom rezervnom kopirovanii.
- Vklyuchit audit and regulyarno eksportirovat otchyoty for kontrolya access.
- Pered izmeneniem portov delat skrin/eksport tekuschikh proxy settings.
- For HTTPS postavit reverse proxy/IIS with sertifikatom and ogranichit pryamoy access k HTTP-portu 5080.
- Before upgrading RSG, stop the proxy, back up ProgramData\RSG, update the files, start the service and run RS version detection.
Illyustratsiya 1. overview — consolidated tablitsa naznacheniy access
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Overview item 1 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Overview item 2 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Overview item 3 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Overview item 4 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Overview item 5 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Overview item 6 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Overview item 7 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Overview item 8 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Overview item 9 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Overview item 10 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Overview item 11 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Overview item 12 | Represents or controls this part of the Overview screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 2. Users — reestr identichnostey and naznacheniya
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Users item 1 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Users item 2 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Users item 3 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Users item 4 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Users item 5 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Users item 6 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Users item 7 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Users item 8 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Users item 9 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Users item 10 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Users item 11 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Users item 12 | Represents or controls this part of the Users screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 3. projects — catalog RS, struktura and accessy
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Projects item 1 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Projects item 2 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Projects item 3 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Projects item 4 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Projects item 5 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Projects item 6 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Projects item 7 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Projects item 8 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Projects item 9 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Projects item 10 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Projects item 11 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Projects item 12 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 4. roles — matritsa prav by razdelam
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Roles item 1 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Roles item 2 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Roles item 3 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Roles item 4 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Roles item 5 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Roles item 6 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Roles item 7 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Roles item 8 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Roles item 9 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Roles item 10 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Roles item 11 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Roles item 12 | Represents or controls this part of the Roles screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 5. Sections — catalog distsiplin and privyazki
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Projects item 1 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Sections item 2 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Sections item 3 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Sections item 4 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Sections item 5 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Sections item 6 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Sections item 7 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Sections item 8 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Sections item 9 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Sections item 10 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Sections item 11 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Sections item 12 | Represents or controls this part of the Sections screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 6. Shlyuzy RS — management proxy and zaschitoy
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Projects item 1 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | RS gateways item 2 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | RS gateways item 3 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | RS gateways item 4 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | RS gateways item 5 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | RS gateways item 6 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | RS gateways item 7 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | RS gateways item 8 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | RS gateways item 9 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | RS gateways item 10 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Users item 6 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | RS gateways item 12 | Represents or controls this part of the RS gateways screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 7. Bekapy — setka rezervnogo kopirovaniya projectov
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Projects item 1 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Backups item 2 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Projects item 5 | Represents or controls this part of the Projects screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Backups item 4 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Backups item 5 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Backups item 6 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Backups item 7 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Backups item 8 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Backups item 9 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Backups item 10 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Backups item 11 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Backups item 12 | Represents or controls this part of the Backups screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 8. Zhurnal audita — potok sobytiy and eksport
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Audit log item 1 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Audit log item 2 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Audit log item 3 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Audit log item 4 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Audit log item 5 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Audit log item 6 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Audit log item 7 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Audit log item 8 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Dayot response on vopros «kto izmenil access». Imena in itogovom dokumente zamaskirovany. |
9 | Audit log item 9 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Audit log item 10 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Audit log item 11 | Represents or controls this part of the Audit log screen. | Stroka details formiruetsya serverom; for chuvstvitelnykh znacheniy in dokumente primenena maskirovka. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Audit log item 12 | Represents or controls this part of the Audit log screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illustration 9. Statistics — activity analytics and reports
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Statistics item 1 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Statistics item 2 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Audit log item 3 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Statistics item 4 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Statistics item 5 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Statistics item 6 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Statistics item 7 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Statistics item 8 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Statistics item 9 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Statistics item 10 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Statistics item 11 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | Statistics item 12 | Represents or controls this part of the Statistics screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
Privatnost: in izobrazhenii skryty imena users, nazvaniya projectov and/or chuvstvitelnye znacheniya, if oni prisutstvovali on screene.
Illyustratsiya 10. Konfiguratsiya — sistemnye settings, license and vneshniy vid
Annotirovannaya version: personalnye znacheniya in tablitsakh/polyakh zamaskirovany; vynoski vyneseny za predely interface.
Podrobnaya legenda
№ | Element | What it does | How it works | Why it is needed |
1 | Configuration item 1 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
2 | Configuration item 2 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
3 | Configuration item 3 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
4 | Configuration item 4 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
5 | Configuration item 5 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
6 | Configuration item 6 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
7 | Configuration item 7 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
8 | Configuration item 8 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
9 | Configuration item 9 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
10 | Configuration item 10 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
11 | Configuration item 11 | Represents or controls this part of the Configuration screen. | Works through the current filters, selection, and RSG API data. | Helps the administrator manage this area faster and with fewer configuration errors. |
12 | buttons sokhraneniya parolya | Save a new password or remove the existing one. | Obrabotchik validiruet sovpadenie poley and vyzyvaet API smeny parolya. | Predotvraschaet sluchaynoe raskhozhdenie parolya and podtverzhdeniya. |
Khotite izuchit vtoruyu chast documentation?
Pereyti k kompleksnomu analysisu →