CloudThinker
  • Get Started
    • Welcome to CloudThinker
    • Key Features
    • Announcements
      • CloudThinker Beta Launch
  • Quick Start
  • HOW TO GUIDE
    • Workspace
      • Setup Your Workspace
    • Knowledge Base
      • CloudThinker Knowledge Base Guide
    • Agent Orchestration
      • Multi-agents orchestration
        • CloudThinker Prompting Guide
      • Agent
        • Build your own Agents
        • Tony - Database Engineer
        • Kai - Kubernetes Engineer
        • Alex - Cloud Engineer
        • Anna - General Manager
      • Connectors
        • MCP Manager
        • Model Context Protocol (MCP)
      • Memory
  • Task Management
    • Schedule Tasks
  • Management
    • Slack Integration
  • Management
    • User Roles & Permissions
    • Payment & Subscription
  • Learn More
    • Prompting Tips
    • Trouble Shooting
Powered by GitBook
On this page
  • Structure
  • Permission Comparison
  • Rationale and Benefits
  1. Management

User Roles & Permissions

Coming soon

Structure

CloudThinker uses a workspace-based structure to organize users and manage permissions. Each workspace is set up as follows:

  • 1 Owner

  • 1 Admin

  • 1 or more Developers

This structure ensures clear lines of responsibility and appropriate access levels for effective user management.

Permission Comparison

Action
Owner
Admin
Developer

View Dashboard

x

x

x

View Resources tab

x

x

x

View Operate tab

x

x

x

View Monitor tab

x

x

x

View Agents

x

x

x

View Workspace Setting

x

x

x

View Users in Workspace

x

x

x

Edit Knowledge Base

x

x

x

Edit Agents

x

x

x

Edit Schedule Tasks

x

x

x

Edit Connectors

x

x

x

Edit Integrations

x

x

x

Edit Workspace Setting

x

x

Edit Users in Workspace

x

x

View Subscription Management

x

View Payment Management

x

Edit Subscription Management

x

Transfer Workspace Ownership

x

Rationale and Benefits

This role-based access control system is designed to:

  1. Ensure financial control remains with the workspace owner

  2. Allow efficient management of the workspace by the admin

  3. Provide developers with the access they need without risking accidental changes to crucial settings

By structuring permissions this way, we support effective cloud cost optimization by:

  • Maintaining clear oversight of financial aspects (Owner)

  • Enabling strong day-to-day management of cloud optimization efforts (Admin)

  • Allowing hands-on use of CloudThinker without risking workspace integrity (Developer)

This structure promotes collaboration while maintaining appropriate access controls, crucial for managing and optimizing cloud costs effectively.

PreviousSlack IntegrationNextPayment & Subscription

Last updated 1 month ago