You gave someone access to a connector, but it's not showing up in their space. Or a space's connectors list looks empty even though the connector clearly exists. This is almost always the same thing at work, and once you understand the rule behind it, the fix is quick.
Note: A connector, skill, or network is only usable in a space when everyone who has access to that space also has the right access to that resource.
So availability isn't about any single person. It's about the whole space. If even one member of the space is missing access to the connector, the connector won't be available there for anyone.
Why it works this way
Connectors hold credentials, and skills and networks grant real capabilities. If a connector became usable in a space the moment one person had access, then everyone who can build in that space could use its credentials, including people you never granted it to.
Tying availability to every space member keeps access honest: a resource shows up in a space only when everyone there was actually meant to have it. Tines 3B works this out from your grants automatically, so there's nothing to keep in sync manually.
What "everyone" needs, by resource
The exact requirement depends on the resource and on what each person does in the space:
Connectors. People who build or run workflows in the space need to be able to use the connector. People who only view or administer the space need to be able to view it.
Skills. Everyone with access to the space needs at least view access to the skill.
Networks. People who can build or run workflows in the space need to be able to use the network.
If someone in the space falls short of this, the resource stays unavailable there until their access is topped up.
How to make a resource available
You have a few ways to line access up. Any one of them works:
Add the resource to the space. On the space's access tab, add the connector, skill, or network. This grants everyone with space access what they need in one step.
Add the space to the resource. On the connector's or skill's access tab, add the space. This grants that space's members access to the resource.
Match the grants yourself. Give the same people and groups access to both the space and the resource.
The simplest habit is to grant access through groups and use the same group on both sides. Add a new person to the group, and their access to the space and the resource stay lined up automatically.
Why adding a member can prompt you or get blocked
Because availability depends on every member, adding someone to a space can affect what that space can use. If you add a member who lacks access to a connector or skill the space already relies on, Tines 3B will prompt you to grant them that access too, so the space keeps working.
Approving keeps everything running. If you'd rather not, you can add them without it, but be aware the resource may no longer be available in that space.
Common symptoms and what they mean
"The connectors list in my space is empty." Not every member of the space can use those connectors yet. This is exactly what the space's own hint means when it says connectors appear once every member with space access can also use them.
"I gave one builder access, but the connector still isn't usable in the space." Another member of the space is still missing access. Availability needs all of them, not just one.
"It works in my personal chat but not in the shared space." In your personal space and personal chats, you only need your own access to a resource. A shared space has the stricter, everyone-must-have-it rule.
Where to check
Two screens tell you the current state:
A space's access tab lists the connectors, skills, and networks that space can currently use.
A connector's or skill's access tab lists the spaces that can currently use it.
If a resource isn't in the list you expect, that's your sign that a member somewhere is missing access. Grant it using one of the methods above, and the resource will appear.