Customize your Team dashboard
Fork Tourtois, accept a Release and choose the App your Team opens on.
Your Team opens on its dashboard at its own address, such as
garden.fungi.computer. The default is Tourtois, an App that opens your
other Apps and arranges their windows. You can change Tourtois or choose another
available App as the dashboard.
You need to own the Team to fork, build, accept Releases and change this selection. Members use the dashboard the owner chooses. An Agent can carry out approved source and publication work only with the owner’s explicit delegated authority.
Fork and change Tourtois
Section titled “Fork and change Tourtois”- Open App releases in Team settings.
- Choose Tourtois under Platform App, then Create source fork.
- Select the resulting Team App and note its repository.
- Edit and push that fork’s source on
main. Keep its captured recipe and dependencies. For a first change, alter an App-owned label without changing its capabilities or host integration. - Choose Build Computer and Build current revision. Check the source revision, digest and Release ID when the candidate appears.
Tourtois also offers Fork Tourtois in its advanced App settings. That control creates the same kind of Team-owned source fork and provides Open Team Git access. Continue building and accepting it through App releases.
A build leaves the live dashboard alone. Use Preview candidate to inspect the new page before acceptance. Preview has no Team resource permissions, so it cannot qualify the real directory, child-App launches or Agent access.
Choose the existing dashboard App under App to replace, then Accept release to select the candidate for this Team. Check the acceptance result and reopen the workspace. Test opening another App and switching focus before sharing the change with your Team.
Choose another dashboard App
Section titled “Choose another dashboard App”In the Team workspace, choose an available App under Team dashboard App. Only Apps with an available selected Release and visual surface appear as usable choices. The selected App replaces Tourtois as the dashboard.
Choosing an App changes which App opens. It does not approve file, Agent, generation or child-App-hosting access. An App needs the declared and granted capabilities for the dashboard features it implements. Tourtois asks the host to mount each child under that child’s own identity and permissions.
Opening Settings from Tourtois uses host-rendered controls and your signed-in authority. The dashboard App does not gain administration rights by showing that entry point.
Reset and recover
Section titled “Reset and recover”Reset to Tourtois clears the custom dashboard choice. The Hub also offers it when the selected dashboard cannot open, so recovery does not depend on that App rendering its own settings. Your fork and saved source remain.
Resetting the dashboard choice does not undo a Release override you accepted for the Team’s default dashboard App. If that Release is the problem, restore its selection separately through App settings. Keep a known-good Release ID before replacing it. A revoked Release is not a usable recovery choice.
If acceptance or selection conflicts, refresh the current App and workspace facts before trying again. If the request’s outcome is uncertain, read the selected Release first. Do not assume an error means the old dashboard stayed selected.
Tourtois runs on the App origin and connects through Agar. It does not receive Team sign-in cookies or its children’s grants. Layout and focus arrange windows. They do not retarget another App’s accepted work or change an Agent’s Home.