What a profile holds
You can configure more than one profile per connector, for example, an API Key profile for some accounts and an OAuth profile for others. The default profile decides which authentication fields appear in the Hub.
Shared vs restricted
Every profile is either Shared, so anyone in the project who can link accounts may use it, or Restricted, so only the members and groups granted access can. A restricted profile is hidden from the linking flow for everyone else. Restricting controls use, not governance: project admins still view, edit, and delete the profile either way. See Sharing Connector Profiles.Scoping Connectors
Set up authentication, then choose which actions and events a profile exposes.
Use Your Own OAuth Apps
Register your own OAuth app instead of using StackOne’s shared credentials.
Connector Versioning
Pin a profile to a connector version so its behavior stays fixed.
Managing Connectors
Configure, secure, and version the connectors your projects use.
Connection issues behind a firewall
If a provider API or webhook endpoint is behind a firewall, allow inbound traffic from these StackOne IP addresses:
Requests from your infrastructure to the StackOne API may pass through AWS edge locations. If your firewall restricts outbound traffic, allow HTTPS traffic to the AWS edge location ranges and the StackOne IP addresses above.
StackOne may add or remove IP addresses when regions or infrastructure change. Check this list when updating your firewall rules. Requests from StackOne use HTTPS with TLS 1.2 or later.