A shared space for multiple users in the same account or organization, using the same saved resources, settings, and team-owned assets instead of everyone working completely separately.
Workspace-wide history that lets approved users see runs created by other members of the same workspace, with proper membership checks, permissions, and polished filtering.
A way to create, name, revoke, and track API keys for calling the product programmatically, replacing local testing shortcuts with a real way to authenticate API requests.
Account activity and consumption details, such as request counts, rows processed, API usage, failures, or how close the account is to plan limits.
Different permission levels for team members, such as ownership, admin access, standard member access, or view-only access, depending on what each person should be allowed to manage or use.