Projects
Projects provide data isolation and access control to collections of resources within an organization. Every recording, device, and event belongs to one Project.
Projects are currently in beta. Contact us at [email protected] for early access.
What can you do with Projects?
Projects enable you to organize data and control access within your organization.
- Separate production and development workflows
- Organize data by team or customer
- Share subsets of data with specific members
Creating a Project
Every organization starts with a single Project. Admins of enterprise organizations can create additional Projects from the Projects page.
When creating a new Project:
- All data remains available under existing Projects.
- Members retain their current access to Projects.
Before creating a second Project, ensure all programmatic uploads specify a Project or existing device. See below.
Access control
Admins can assign members to Projects via the Members page.
- Members with the user role can only see and access Projects they are assigned to.
- Members with the admin role can access all Projects.
- API Keys can access all Projects.
Projects are isolated. Data in one Project cannot be accessed from or moved to another Project.
Associating data
We recommend always providing a Project ID when interacting with Foxglove programmatically. For organizations with multiple Projects, a Project ID is required when creating devices or uploading recordings without an existing device.
Project IDs can be found on the Projects page.
API requests
Endpoints that create or list Project scoped resources accept a projectId field to specify the Project. See API docs for more information.
Self-hosted Primary Sites
Providing a foxglove_project_id record in object metadata or a projectId in MCAP metadata associates the upload with a Project. See Site docs for more information.
Self-hosted Primary Sites support Projects as of version 0.0.69.
Web and desktop apps
Uploading files and creating devices from the Foxglove dashboard automatically associates them with the current Project.
Project vs Organization scoped resources
Every device, event, and recording belongs to a single Project. Data in one Project cannot be accessed from another Project.
Resources at the organization level work across all Projects.
| Resource | Project | Organization |
|---|---|---|
| Devices | ✓ | |
| Events | ✓ | |
| Recordings | ✓ | |
| API Keys | ✓ | |
| Custom Properties | ✓ | |
| Extensions | ✓ | |
| Layouts | ✓ | |
| Sites | ✓ | |
| Webhooks | ✓ |