steedos-object-permissions

Automate Steedas multi-level permissions across object, field, and row-level YAML files.

1.6k|413|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/steedos/steedos-platform --skill steedos-object-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steedos-object-permissions
Source: https://github.com/steedos/steedos-platform/tree/main/skills/steedos-object-permissions
Command: npx skills add https://github.com/steedos/steedos-platform --skill steedos-object-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Steedos enables multi-level permission control by defining object-level, field-level, and row-level restrictions using dedicated YAML files (.permission.yml, .permissionset.yml, .profile.yml, .role.yml, .restrictionRule.yml). This Skill guides on how to set up and reason about who can create, read, edit, or delete records, and how to structure permissions across objects.

Core Features & Use Cases

  • Object-level permissions via .permission.yml
  • Field-level permissions via field_permissions
  • Row-level/restriction rules via restrictionRules
  • Manage permission sets, profiles, and roles for teams
  • Clear guidance on typical governance scenarios

Quick Start

Create a sample orders.user.permission.yml under an object's permissions directory to grant read access.

Frequently Asked Questions about steedos-object-permissions

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

FAQPage Schema
How do I configure Steedos object permissions for read and edit access?

Steedos object permissions support multi-level control by defining object-level access in .permission.yml, field-level visibility in field_permissions, and row-level data filtering through restrictionRule.yml files.

What is the best way to set up field-level permissions in Steedos?

Set up field-level permissions in Steedos using the field_permissions attribute within your YAML configuration files. This restricts access to specific object fields, ensuring users only view or modify data fields they are authorized to access.

Can I use YAML files to manage Steedos permission sets, profiles, and roles?

Yes, you can manage Steedos permission sets, profiles, and roles by defining configurations in .permissionset.yml, .profile.yml, and .role.yml files. These files structure team governance and access control across objects systematically.

How do restriction rules work for row-level access control in Steedos?

Steedos restriction rules work by applying row-level filters defined in restrictionRule.yml files, controlling which specific records a user can access based on defined criteria, complementing object and field-level permissions.

Does Steedos support unified permission configuration across multiple levels?

Yes, Steedos supports unified multi-level permission configuration by automating settings across object, field, and row-level controls using dedicated YAML files like .permission.yml and .restrictionRule.yml for comprehensive access governance.