Limitations
In AI-School, you can set various limitations to regulate the use of the application. These limitations help manage costs and promote responsible use by employees.
Limits
Soft Limits
Soft limits are warning limits that inform users when they are approaching or have reached their assigned quota. These limits:
- Show warning messages to users
- Do not fully restrict usage
- Serve as a guideline for responsible use
- Can be exceeded by the user
Examples of soft limits:
- 20 images per day
- 200 chat messages per day
Hard Limits
Hard limits are strict restrictions that cannot be exceeded. When a hard limit is reached:
- Users cannot send new chat messages
- Users cannot generate new images
- Access to the relevant functionality is completely blocked
- Must wait until the limit is reset (for example, the next day)
Hard limits are optional and can be set in addition to soft limits for extra control.
Enabling Features
In addition to limitations, you can also determine which features are available to employees in your environment.
Available Features
Enable Voice Chat
- Functionality: Enables communication with the AI using voice
- Configuration: Can be enabled for all employees in the environment
- Use: Users can convert their voice to text and have AI responses read aloud
Enable MCP Links
- Functionality: Model Context Protocol links for extended AI functionalities
- Configuration: Can be enabled for all employees in the environment
- Use: Provides access to advanced AI tools and integrations
Individual Feature Access
In addition to the general settings, you can also manage features at the individual level:
Access for Individual Employees
- Go to Employees in the management environment
- Select the desired employee
- Adjust the feature settings for this specific employee
- These settings override the general settings
Flexible Configuration
This approach allows you to:
- Disable features for the entire environment
- Provide selective access to specific users
- Set up pilot programs with a limited group of users
- Gradual rollout of new functionalities
Example scenario: You can disable MCP links for all employees, but enable them for a select group of power users participating in a pilot program.
Best Practices
- Gradual rollout: Start by enabling features for a limited group before making them available to everyone
- Training: Ensure users are trained in using new features before enabling them
- Monitoring: Keep track of feature usage through reports in the management environment
Configuration
All limitations are set via the management environment under the "Limitations" menu item when setting up a new environment or editing an existing one.
Steps to set limitations:
- Go to the management environment
- Select "Environment" in the menu
- Navigate to the "Limitations" step
- Set the desired soft limits
- Optionally enable and set hard limits
- Configure the desired features for employees
- Settings are saved after each step