Seats and Teams
Adding members, roles and permissions, shared workspaces and centralised billing.
A team is a billing and sharing boundary. The owner adds seats, invites members by email, and every seat carries the full plan entitlement for that person. Seats are per person and not shared: two people on one login will trip the concurrent session check, and real-time market data entitlements are granted per named user under the exchange agreements.
Roles are owner, admin, member and viewer. Owners control billing and can transfer ownership. Admins manage seats, shared content and integration keys. Members create and share their own work. Viewers can open what has been shared with them but cannot modify it, which is the right role for a compliance reviewer or a client.
Shared workspaces hold watchlists, chart layouts, screeners, alert templates and scripts that belong to the team rather than to a person. Anything in a workspace survives someone leaving, which is the point — an alert that fires into a desk channel should not disappear because its author changed jobs. Permissions are set per item and inherit from the workspace by default.
Billing is centralised on the team. One invoice, one payment method, seat count adjustable at any time with proration on additions and credit on removals at the period boundary. Usage against API and export allowances is pooled across the team and broken out per member in the usage view, so it is clear who is generating the load before anyone has to ask.