Skip to main content
An organization is the unit that owns members, projects, billing, and usage in AskTable. One account can join multiple organizations, while every project belongs to exactly one organization.

​
Cloud and self-hosted

​
Switch organizations

Open your profile card in the lower-left corner and select an organization. Project lists, remembered projects, billing, and usage all follow the active organization and never mix data from another organization. Self-hosted deployments have one organization, so the profile card has neither an organization switcher nor a separate organization-governance entry. Open Profile first, then use the Organization section in personal settings. If your account has no organization, AskTable opens onboarding after sign-in. You can create an organization, accept a direct invitation, or open an organization or project invite link.

​
Project visibility

Projects have two visibility types:
  • Public projects: active organization Owners, Admins, and Members inherit the project’s default Admin or Member permission.
  • Private projects: only people explicitly added to the project can enter.
  • Guests never inherit a public default and must still be added explicitly.
  • Billing Admins can view and manage the plan and review usage, but cannot enter projects.
“Public” means public inside the current organization, not public on the internet. An explicit project role always overrides the public default in either direction. Removing that explicit role restores the current default permission. Owners and Admins can always create projects. Whether Members can create projects is controlled by the organization’s Allow members to create projects setting.

​
Management entry points

Owners and Admins can open Organization settings, Project management, Member management, Usage, and Enterprise integrations from personal settings. Billing Admins see only Organization settings and Usage; Organization settings shows the plan, expiration, and quotas without exposing basic organization details. Project management creates and renames projects and governs explicit project members and ownership. An organization administrator without an effective project role can govern metadata but cannot open project content. The explicit project owner can also edit visibility and the default permission in project settings. Member management changes organization invitations, membership roles, deactivation, and ownership transfer only. It never edits sign-in email, password, or system-administrator status. Cloud SYS_ADMIN users still have system-level pages for global projects and users; that scope is separate from the current organization. Self-hosted deployments omit those global pages and govern users and projects inside their single organization. A self-hosted SYS_ADMIN can also review trial or License status and activate or update an enterprise license from Organization settings inside personal settings. Owners/Admins can also connect WeCom or WPS, pre-import members, and copy the organization-specific login link under Enterprise integrations. Google, GitHub, WeChat, email, and SMTP are deployment-level environment configuration and no longer appear in System settings.

​
Conversations and dashboards

Conversations and dashboards are visible to their creator by default. People with an effective project Owner or Admin role can view all project content. Organization Owners/Admins gain that content permission only through an explicit project role or a public project’s default Admin role. Use a share link when someone else needs access.
A share link does not add its visitor to the organization or project. Existing links stop working if the organization is suspended or deleted.

​
Next steps