Sharing with your team and publicly

Making your tiles publicly discoverable in the Tessl Registry

Tiles can be shared with your team or with the entire internet. This is controlled by the private field in your tile's tile.json file.

Understanding public vs private tiles

Private tiles ("private": true) - Default

Shared only with your team:

• Only accessible to workspace members

• Not discoverable in public searches

• Useful for proprietary code, internal standards, company-specific content

• Team sharing: Add members to your workspace to give them access

If you don't specify the private field in your tile.json, it defaults to true (private).

Public tiles ("private": false)

Shared with the entire internet:

• Anyone can discover and install them via the Tessl Registry

• Appear in search results and on your workspace's public profile

• Useful for open source libraries, shared standards, community resources

• Cannot be made private again once published

Making a tile public

Warning: Once you make a tile public, you cannot make it private again. Use this with caution.

To make a tile publicly discoverable, set "private": false in your tile.json:

{
  "name": "myworkspace/my-tile",
  "version": "1.0.0",
  "summary": "My public tile",
  "private": false,
  "docs": "docs/index.md"
}

Then publish (or republish) your tile:

tessl tile publish

Your tile is now publicly discoverable in the Tessl Registry and accessible to anyone on the internet.

Best practices

• Start private - Develop and test tiles privately before making them public

• Use semantic versioning - Especially important for public tiles that others depend on

• Document thoroughly - Include clear README files and usage examples

• Validate before publishing - Run tessl tile lint to check for issues

Related documentation

• Distributing via registry - How to publish tiles

• Configuration files - tile.json field reference

• Creating tiles - How to create your own tiles