simulator-access

Manage and revoke access rules for Simulator.Company objects across workspaces.

58|9|Updated May 5, 2026
One-click install
npx skills add https://github.com/corezoid/simulator-ai-plugin --skill simulator-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simulator-access
Source: https://github.com/corezoid/simulator-ai-plugin/tree/main/plugins/simulator/skills/simulator-access
Command: npx skills add https://github.com/corezoid/simulator-ai-plugin --skill simulator-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Administrators need a clear, auditable way to control who can view, modify, or execute actions on Simulator.Company objects (actor, form, account, template, tree layer) and to share or revoke access across a workspace.

Core Features & Use Cases

  • Centralized access governance for objects, including view/modify/delete/sign/ds/execute privileges, with optional cascading to child objects.
  • Readable audit trails of current permissions and the ability to update permissions in bulk or per object.
  • Use cases include granting access to a teammate, revoking permissions when a user leaves, or applying the same rules across multiple layers or accounts.

Quick Start

Grant a user read and write access to a specific actor by calling the relevant access tool with the proper data.

Frequently Asked Questions about simulator-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage access control for Simulator objects like actors and forms?

You can manage access control by using tools like getAccessRules and saveAccessRules to apply sharing, revocation, and bulk updates across workspace objects including actors, forms, accounts, and tree layers.

Can I grant read and write permissions to a teammate for a specific actor?

Yes, you can grant a user read and write access to a specific Simulator.Company actor by calling the relevant access tool with the proper data, applying view and modify privileges to that object.

What is the best way to revoke permissions when a user leaves the workspace?

The best way to revoke permissions is by using revocation operations on Simulator.Company objects, selectively removing view, modify, delete, sign, and execute privileges to maintain an auditable access governance trail.

Does this access control system support bulk updates across multiple layers and accounts?

Yes, bulk updates are supported across workspace objects. You can apply the same access rules across multiple Simulator.Company layers and accounts, with optional cascading to child objects for permission management.

How does identity resolution work for users, groups, and SA IDs when configuring RBAC?

Identity resolution for users, groups, and SA IDs is supported when applying access rules. This ensures permissions are correctly mapped to the right identities during sharing, revocation, and bulk update operations.

When do I need cascading access rules for child objects?

Cascading is needed when applying permission changes to a parent Simulator.Company object and requiring those view, modify, or execute privileges to automatically apply to its child objects, ensuring consistent hierarchical access control.