Port

What a member can do

• Search the software catalogue: list blueprints, entities and scorecards.
• List self-service actions and workflows, run them and track each run.
• Search audit logs and Port's documentation.
• With a builder role, create and update blueprints, entities, actions, scorecards, dashboards and integration mappings.

Each task names the Port tools it may call. port on a task means every tool the Port server offers; a name such as port.<tool> means that tool alone. A tool the task does not name is refused, whatever the connection allows.

Who connects it

A Port connection acts as the Port account that signed in when it was connected. It can do what that account can do, and no more.

Anyone who may change tools in your enterprise can connect Port for a member or a team. Connecting it for the whole enterprise is for the owner, and the people the owner allows.

A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A connection on anything but a task also reaches the chat of every member it covers.

What waits for you

In a run, nothing on Port waits for you unless the task declares a gate on it. To approve each change before it happens, gate the tools that change something on the task. See Gates and tool scopes.

In a chat, a Port tool that its server does not mark as read-only asks you before it runs, unless you chose Always allow for that member and tool.

Setup

Before you connect

Use this one if your Port account is in the EU region. For the US region, connect Port (US). Port has separate servers for EU accounts (app.port.io) and US accounts (app.us.port.io): connect the one that matches your region. The tools a member gets follow its Port role and permissions.

Connect it

Port is an Express tool, so there is no server address, key or app to set up. Work in one browser window throughout: the sign-in returns to the portal in the window you started from.

1. In the portal, open the member's page → Tools. To connect it for a team or the whole enterprise, open Tools in the sidebar.
2. Under Express, find Port and choose Connect. On the Tools page you are asked who uses it: one member, a team or the whole enterprise.
3. Port's sign-in opens. Sign in with the account the member should work as, and approve what it asks for.
4. You are back on Tools, and Port shows as connected.
5. Name the tools on the task, port for all of them or each by name.
6. Check it. Run a task that reads something from Port. The run page shows the call and what came back.

You can take the access back at any time: delete the connection on Tools, or remove Zero Human OS from the connected apps in your Port account.

A first task to try

With Port connected, give a member a task that uses it. For example:

Every Monday, list the services failing their production-readiness scorecard and what each is missing.

Start this task in the portal. It opens a conversation with your COO with the request written out. Read it, change what you like and send it. The COO asks what it still needs to know, then proposes the task for you to approve: its name, who owns it, its guardrails, the Port tools it may use and its instructions. Nothing is created until you approve it.