Currently, Speckle allows managing models that contain versions and comments, but there is no native way to define custom parameters or attributes at the project level.
It would be highly valuable to have a native “Project Parameters” block that lets users register general project information such as client, address, internal codes, and key dates directly within the Speckle environment.
This would improve project identification, filtering, and connection with reports, external integrations, or automation workflows that use these parameters as input variables.
Proposal
Add a project.metadata field that allows creating and editing key–value pairs directly within each project — visible to project members and accessible through existing Speckle integrations.
Current workaround
Until such functionality exists, a possible alternative is to create a “ProjectMetadata” model inside the project that contains these attributes, and then link that model from an external table, such as Power BI, to include the information in reports.
Benefits
- Centralizes essential project information in one place.
- Improves traceability and coordination between teams.
- Enables process automation and seamless integration with external tools.
- Reduces dependence on external spreadsheets or manual notes.
- Provides structured, reusable context across the Speckle ecosystem.