Skynet
Visit SkynetBlogUse-casesDiscord
  • Getting Started
    • Introduction to Skynet
    • Why Skynet?
    • Features
      • Skynet Intelligence
      • Skynet Orchestration
      • Data Security
      • Memory
      • Skynet Chain
      • Payments
      • AI Tools
    • Skynet Interoperability
  • Agent Studio
    • Studio Overview
    • Dashboard
    • Workflow
  • Skynet Ecosystem
  • Skynet Protocol
    • SkyIDs
    • Role Based Access Control (RBAC)
    • Organizational Services
    • Add AI Agent tools
    • Payment Rails
      • Fiat/Crypto On-ramp
      • Settlement With Tooling Providers
      • Subscriptions vs on-demand Pay-per-second
      • How AI Agents Spend
    • Subnet
      • Types of Subnet
      • Subnet fault-tolerance and security
      • Provider Subnet
      • Provider Subnet functions
      • Tool fees
    • Smart Access Points
  • FAQ
  • Tutorials
  • Concepts
    • Glossary
  • Technical Support
  • Build your Project on Skynet
    • Interact with AI service to create an Agent
      • Prerequisites
      • SDK Initialization
      • Adding Balance to a Subnet
        • Best Practices
        • Common Errors and Solutions
      • Authentication
      • userAuthPayload
      • Service Endpoints
    • Integrate AI agent tools
      • Installation
      • Configuration
      • Initialization and Setup
      • Core Functions
      • Endpoint Summary
  • Developer Portal
Powered by GitBook
On this page
  1. Skynet Protocol

Role Based Access Control (RBAC)

Role Based Access Control (RBAC) within Skynet

Skynet's Role-Based Access Control provides the granularity needed to manage wallets, budgets and agents and their infrastructure in a secure and mature way. This makes it far easier for organizations to work with the protocol and ensure their developers have the appropriate levels of access and audit trails can be preserved.

This RBAC mechanism offers various roles, such as:

  • Read

  • Modifier

  • Access

  • Billing

All these roles help to enhance the control and security of AI agents. An explanation for each:

  • Read Role: AI agents are granted access to read deployments and responses.

  • Modifier Role: Enables AI agents to access, subscribe to, and initiate demand for various tools and services.

  • Access Role: Allows AI agents to manage specific permissions and authorize access to additional tools.

  • Billing Role: Provides AI agents with budgeting oversight and the ability to carry out financial transactions.

Using these roles, AI agents can operate securely and effectively. Each role facilitates different and distinct levels of access and control. This empowers users and ensures that AI agents interact with tools and services based on their designated permissions, increasing security and functionality.

PreviousSkyIDsNextOrganizational Services

Last updated 22 days ago