Share it
Every Helix app sits behind login. A colleague signs in with their Tray account (through your company’s SSO, if you use it), so a forwarded link alone won’t get anyone in.
You set who gets in on the project’s Access Control tab:
- Workspace, the default. Everyone in the project’s workspace, and your org admins.
- Only people invited. People you invite by name, from anywhere in your organization.
- Organization. Everyone in the organization. Only an org admin can pick this.
Invite the CSMs by name, then send them the URL. They can use the app but can’t change or deploy it, and the setting survives later deploys.
What IT sees
The project card shows the app’s name, what it does, the services it calls and who created it. Org admins see it in the Admin console with every other project. When someone asks who built the tracker and what it connects to, the answer’s already there.
Read the logs
Every run of the deployed app is logged, and the assistant can read the logs for you:
A CSM says the renewals page showed an error around 9:15 this morning. Find the failing run in the deployed logs, tell me what went wrong, and propose a fix. Don't deploy anything.The same logs are on the project’s Logs tab. Check the morning refresh the same way: ask, and look for the count of accounts it saved.