list-page

Manage conditional access and view permissions for lists by company, department, and part IDs.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dnsnamdang/hrm-claude-config --skill list-page-dnsnamdang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-page
Source: https://github.com/dnsnamdang/hrm-claude-config/tree/main/thanh_an/.skills/list-page
Command: npx skills add https://github.com/dnsnamdang/hrm-claude-config --skill list-page-dnsnamdang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies access to and viewing comprehensive lists across multiple company, department, and part segments, enhancing efficiency in data management.

Core Features & Use Cases

  • Conditional Access Permissions: Defines and applies permission rules based on company, department, and part IDs for viewing lists.
  • Read-only Access to All: Grants permission to view all records, excluding draft/staging entries.
  • Custom Filtering: Allows filtering and viewing based on specific criteria for company, department, and part IDs.
  • Use Case: Streamline access to employee lists by department, department head, or team, providing a centralized view of the team structure and roles.

Quick Start

Access the comprehensive list for "Company X" under "Department Y" by invoking the list-page skill.

Frequently Asked Questions about list-page

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

FAQPage Schema
How do I implement role-based access control for department and company lists?

You can filter list views based on specific company, department, and part IDs. The custom filtering mechanism ensures users only see the records they are explicitly authorized to view within their organizational segment.

Can I restrict list view permissions to exclude draft and staging entries?

Yes, read-only access can be granted to view all records while automatically excluding draft and staging entries. This ensures data-sensitive applications only expose finalized data to authorized users.

What is the best way to manage team-level data filtering for employee lists?

The best way to manage team-level data filtering is by applying custom access control mechanisms based on department, part, and company IDs. This streamlines access to employee lists and provides a centralized view of team structure.

Does this access control approach work for multi-level organizational oversight?

Yes, conditional access permissions are designed for multi-level organizational oversight. They define and apply permission rules across multiple company, department, and part segments to manage data-sensitive applications effectively.

How do I set up custom permission rules for viewing comprehensive lists across departments?

Custom permission rules are set up by defining conditional access permissions tied to company, department, and part IDs. This allows you to filter and view specific list segments based on your defined organizational criteria.