Skip to content

Commit d13c9f7

Browse files
committed
update ai control docs
1 parent 596efbe commit d13c9f7

File tree

1 file changed

+15
-19
lines changed

1 file changed

+15
-19
lines changed

docs/02-control-ai.md

Lines changed: 15 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Phoenix Code AI Control
2+
title: AI Control for school and work
33
---
44

55
import Tabs from '@theme/Tabs';
66
import TabItem from '@theme/TabItem';
77

8-
# Phoenix Code AI Control
8+
# AI Control for school and work
99

1010
🔐 Disable or manage AI features in Phoenix Code for educational and enterprise environments.
1111

@@ -85,7 +85,7 @@ The `--managedByEmail` parameter is optional but recommended. It provides an adm
8585
```
8686

8787
:::note
88-
The `--managedByEmail` parameter is optional but recommended for administrative contact information.
88+
The `--managedByEmail` parameter is optional but recommended. It provides an administrative contact for managing access to AI and educational features in the future. This email will be linked to your institution's AI management if given.
8989
:::
9090

9191
</TabItem>
@@ -110,7 +110,7 @@ The `--managedByEmail` parameter is optional but recommended for administrative
110110
```
111111

112112
:::note
113-
The `--managedByEmail` parameter is optional but recommended for administrative contact information.
113+
The `--managedByEmail` parameter is optional but recommended. It provides an administrative contact for managing access to AI and educational features in the future. This email will be linked to your institution's AI management if given.
114114
:::
115115

116116
</TabItem>
@@ -122,8 +122,8 @@ All installation scripts support the same command-line options:
122122

123123
| Option | Description |
124124
|--------|-------------|
125-
| `--help` | Display usage information and help text |
126-
| `--managedByEmail <email>` | Optional but recommended. Admin email who manages AI policy. Can be used in your Phoenix managed AI dashboard to selectively enable features and manage usage quotas |
125+
| `--help` | Display help |
126+
| `--managedByEmail <email>` | Optional but recommended. Admin email who manages AI policy. Can be used in your Phoenix managed AI dashboard to selectively enable features and manage usage quotas in the future.|
127127
| `--allowedUsers "<user1,user2,...>"` | Comma-separated list of usernames allowed to use AI even when disabled for others |
128128
| `--disableAI` | If present, AI will be disabled by default for all users except those specified in `allowedUsers` |
129129

@@ -336,15 +336,19 @@ The browser version of Phoenix Code will automatically detect if the domain is u
336336

337337
**Q: When will AI be enabled in Phoenix Code?**
338338

339-
Phoenix Code AI will be rolled out after May 20, 2025. Educational institutions should configure AI controls campus-wide before this date.
339+
Phoenix Code AI will be rolled out after **`May 20, 2025`**. Educational institutions should configure AI controls campus-wide before this date.
340340

341341
**Q: How do I know if AI control is working?**
342342

343343
In both the desktop and browser versions, go to View → AI Control Status to see a detailed report.
344344

345-
**Q: Can I allow specific users to access AI features?**
345+
**Q: Can I disable AI for some users but enable it for others?**
346+
347+
Yes, use the `--disableAI` flag to disable AI globally, then use the `--allowedUsers` parameter to specify which users should still have access. Example:
346348

347-
Yes, but only in the desktop version. Use the `--allowedUsers` parameter with a comma-separated list of usernames when running the installation script. These users will be able to access AI features even when disabled system-wide with the `--disableAI` flag.
349+
```bash
350+
sudo ./setup_phoenix_ai_control_linux.sh --disableAI --allowedUsers "teacher1,admin2"
351+
```
348352

349353
**Q: Is AI control mandatory?**
350354

@@ -401,23 +405,15 @@ sudo ./setup_phoenix_ai_control_linux.sh --managedByEmail [email protected]
401405

402406
**Q: What's the difference between browser and desktop control?**
403407
- **Browser Version**: Only supports network-level blocking of `ai.phcode.dev` through your firewall
404-
- **Desktop Version**: Provides comprehensive control through configuration files with user-specific permissions
408+
- **Desktop Version**: Provides comprehensive control with user-specific permissions
405409

406410
**Q: Does this completely prevent AI usage?**
407411
- **Desktop Version**: Yes, the control is comprehensive when properly configured using the installation scripts
408412
- **Browser Version**: Only if you implement network-level blocking of the `ai.phcode.dev` domain
409413

410414
**Q: How can I verify that the firewall is properly blocking AI access?**
411415

412-
In the browser version, use the View → AI Control Status option which will attempt to connect to the AI service and report whether it's accessible or blocked.
413-
414-
**Q: Can I disable AI for some users but enable it for others?**
415-
416-
Yes, use the `--disableAI` flag to disable AI globally, then use the `--allowedUsers` parameter to specify which users should still have access. Example:
417-
418-
```bash
419-
sudo ./setup_phoenix_ai_control_linux.sh --disableAI --allowedUsers "teacher1,admin2"
420-
```
416+
In the browser app at https://phcode.dev, install the `Phoenix Code AI Control`extension. Use the `View → AI Control Status` option. It will report whether AI is accessible or blocked.
421417

422418
**Q: Is there a way to monitor AI usage in my organization?**
423419

0 commit comments

Comments
 (0)