From a private idea to a shared team tool
A small internal tool is most useful when the next person can actually use it. Laplace brings the steps from a private prototype to a shared app into the same workspace.
1. Begin with a focused job
Choose one task: collect requests, track a process, or give your team a simple view of shared information. Describe the job in the app builder, check the preview, and refine the details before publishing.
The preview gives you room to experiment. Saving a draft and publishing a working version are separate steps.
2. Decide who needs access
Apps start private. Use viewer access for someone who needs to open and use the app, and editor access for a collaborator who needs to help build it.
Email invitations can include people outside your organization. This is useful when the work includes a client, a contractor, or another team. Share the app link with the people you have invited so they can return to it.
3. Keep credentials in their own place
Use the secret vault to organize project variables instead of placing sensitive values in an app's interface or a shared message. Values are encrypted, and project folders help you keep related variables together.
When another person needs a secret, create a share link with an expiry. You can revoke that link when the task is finished.
4. Give AI tools a defined role
Connect a compatible AI client through MCP and authorize the access needed for the job. Keep app collaboration, provider connections, and secrets deliberate as you extend the tool.
The same principle applies to a custom browser connection: review the proposed tools before approving them. Start with a narrow task and check the result as you work.
5. Publish and improve
Publish the version you want collaborators to use. The stable app link gives everyone a common place to return to while you continue improving the tool.