How to share an internal tool with your team

The short answer

To share an internal tool, put it online, keep it private, and give each teammate access through their own account. With Boat House, your connected coding agent can deploy the app and invite the people you name. You can ask in plain English.

Suppose you built a project tracker for a small agency. The owner needs to change the software, project managers need to update tasks, and a colleague only needs to read progress. Sending everyone a copy of the files would create separate versions. Sharing one hosted app keeps the work in the same place.

This is an illustrative example. The demo shows a real Boat House platform walkthrough using fictional tutoring data.

Start with one live app

If your tool only runs in a local preview, first connect your agent and deploy it. Open the published link and test a normal task. For an internal tool, keep the app private instead of making it publicly accessible.

Then tell your agent who should use it. For example: “Share the project tracker with Taylor as an editor and Morgan as a viewer.” Give the agent their email addresses when it asks. You choose the recipients; the agent handles the sharing steps.

Start with one teammate and check what they can see and change. Once that works, invite the rest of your team.

Choose the right access

Boat House controls who can open the app and passes the user's role to it. The application must use that role correctly for its own read and write operations. Ask your agent to check this, especially if you are moving an app that did not previously support different roles.

Test the viewer experience with sample data before relying on it. A label that says “Viewer” is not a substitute for enforcing permissions inside the app.

Your teammate opens the invitation

A teammate follows the access link and signs in or completes the account setup. They then use the app in a browser. They do not need your Claude Code session, your connection code, or your hosting credentials.

Do not forward your own account password or agent connection message as a shortcut. Each person should have the access intended for them.

Let another developer improve the software

For someone who will change the app itself, give appropriate Admin access and have them connect their own coding agent. Their agent can work with the source and publish updates. This is a different responsibility from editing a record in the app.

Ask the developer to test the change and preserve existing data before publishing. Use the deployment and rollback documentation when planning a release.

Change access when the team changes

Ask your agent to remove a person who no longer needs the tool or change their role when their responsibilities change. Check that access has actually changed by testing the relevant account.

Boat House's hosted price is per running tool, with no per-person seat charge. The software is open source if you prefer to run it yourself. Review the security page for the platform's controls, shared responsibilities, and limitations.