Profiles
A profile is the endpoint your AI client actually uses. It pins one connection, exposes a chosen tool set, and is shared with specific members. It is the URL you paste into the client.
Why profiles exist
A connection is "what is authorised". A profile is "what a person gets". Two people on the same connection can have different profiles: one with the full tool set, one with a read-only slice. That is what lets you share a connection widely while keeping each person's endpoint scoped to what they should touch.
Profile access is granted to individual members, not to whole roles. Being an admin lets you edit who is on a profile; it does not automatically put you on every profile. See Assign members.
Who sees which profiles
Owners and admins see every profile in the workspace. A member sees only the profiles they created or were assigned to, so the Profiles page shows them their own working set rather than the whole workspace.
A member can open a profile someone else created, but not change it. The fields are read only and there is no delete, which lets you share an endpoint without handing over control of what it exposes. See Permissions if you want to tighten that further.
Endpoints follow the slugs
A profile's MCP endpoint is built from the workspace slug and the profile slug:
https://mcp.floconnector.com/{workspace}/{profile}Change nothing about the URL by hand. Copy it from the profile in the dashboard.