Workspace Settings

The “Workspace” group in Settings (General / Members / Connectors / Activity) is where you manage settings that affect the whole workspace. Most operations require owner permission. The “Usage” pane and, for organization owners and admins, the “Organization settings” entry sit in the “Organization” group underneath. Settings opens as a dialog over the page you are on. A link of the form https://neo.jinba.io/w/<workspace ID>/settings?tab=members opens the dialog straight on that pane (tab can be account, memory, appearance, workspace, members, connectors, activity, or usage); once it is open, the address bar shows the workspace home again. On a narrow screen the same panes open as a sheet, without the Connectors pane and the Organization entry.

​

Workspace info

• Workspace name — shown in the sidebar, the account menu, and shared agents (owners only)
• Workspace ID — used for things like jinba-flow MCP server integration. It is also the /w/<workspace ID>/ segment that every page URL now carries

​

Default model

The model used for new chats started without an agent (ad-hoc chats).

• Changes apply only to new chats created afterwards. Existing chats keep running on the model they were created with — an open ad-hoc chat shows a banner offering to switch to the new model (When the agent’s settings change mid-chat)
• Each agent’s model is set in the Settings section of that agent’s configuration panel
• A default saved on an older generation (Sonnet 5, Sonnet 4.6, …) is not left there: new ad-hoc chats run on the newest generation of the same line, the picker shows that model, and a new agent created in the workspace starts on it too. The first time the composer’s model badge names a different model than you last saw on that device, a one-time callout says which model it moved from and to, and its “Open settings” link lands on this card (a model you pick here yourself is not announced)

​

Default Skill (for ad-hoc chats)

Skills attached here are used by ad-hoc chats.

• There is a limit on how many can be attached
• Changes take effect from new chats only

​

Member management

The Members tab is a single card with a segmented control across the top — “In workspace,” “Invited,” and “Not added” — so “where does this person stand with this workspace?” is answered in one place. Each segment carries a count. Most actions require owner permission.

​

Inviting by email

The “Invite” button (owners) opens the “Invite a member” dialog, where you enter an email address and a role. When someone signs in with that email address, they are added as a member automatically.

• Invitees do not need to belong to this workspace’s organization — workspace membership itself grants access. Someone invited from outside the organization joins as a guest: they can work in the workspace, but the organization’s shared agents and organization settings stay out of reach, and the workspace carries a “Guest” badge in their workspace switcher
• You cannot invite once the plan’s member limit is reached

​

Invited (pending invitations)

The “Invited” segment lists people who have been invited but haven’t joined yet. Void an invitation with “Revoke.”

​

Not added (organization members)

The “Not added” segment lists members of the organization who are not in this workspace yet, so an owner sees the gap without going looking. It is paged rather than loaded all at once, so it scales to a large organization:

• Add one person with the per-row “Add,” or tick several and use “Add to workspace” (“Select every member shown” and “Clear selection” help when a page holds many)
• “Load more” fetches the next page. A note — “This covers part of the organization. Load more to keep looking…” — tells you when only part of the directory has been checked so far
• People who already have an account become members right away; people who have never signed in join automatically on their first sign-in. The plan’s member limit applies here too
• When no one outside the workspace turns up, the segment reads “No one outside this workspace turned up in the part of the organization we checked.”

​

Roles

• Change roles with “Promote to owner” and “Demote to member”
• The last owner cannot be demoted. Promote another member first

​

Removing members

Remove members from the member list. To remove another owner, demote them to member first.

​

Connector access

The “Connectors” tab (“Connector access”) lets a workspace owner restrict which external connectors this workspace can use, narrowing further whatever the organization allows. Each connector is a switch with its state underneath: “Available in this workspace.”, “Blocked in this workspace.”, or — when the organization has disabled it — “Disabled by your organization. It can’t be changed in a workspace.” with an “Org-disabled” tag, which a workspace cannot lift. Members see the list read-only (“Only the workspace owner can change connector access.”). Press “Save” to apply.

• The personal connectors listed here are Slack and Notion; the other catalog services are governed at the organization level
• A blocked connector’s card on the Connectors page reads “This connector is blocked by your workspace’s settings.” with a “Blocked” badge; existing connections are not removed, but the AI stops using them until the block is lifted (Connectors overview)

​

Workspace activity

The “Activity” tab is an append-only log of operations in this workspace — agents, skills, knowledge, files, tasks, members, settings and more. Where an operation recorded its before/after values (a workspace rename, the default model, a member’s role, and the like), the row lists them under “Changes” as “name: before → after”. Visible to owners only.

​

Usage

The “Usage” tab (in the “Organization” group) shows your current plan (Free / Standard / Professional / Enterprise), usage bars for credits and storage, and the member count. Credit and storage limits are shared across the whole organization, and the bars read accordingly: the full bar is the organization’s limit, the light red fill is organization-wide usage, and the dark red fill is this workspace’s share — the percentage shown is the organization-wide figure. Hover either fill for a tooltip under the bar that leads with the fill’s colour swatch: “Org-wide usage: n% of the limit” or “This workspace’s usage: n% of the limit”. The credits bar in the account menu at the bottom of the sidebar reads the same way. To change plans, talk to your workspace owner. In a personal organization (the Free plan), credit amounts are shown as US dollars instead of credits: the rows read “Usage (USD)” and “Org usage (monthly, USD)”, the bar in the account menu is labelled “Org usage”, and the task history shows each run’s usage in dollars. The monthly allowance of a personal organization is $3.00. If your organization has been granted additional credit packs (top-ups beyond the plan), they are drawn on automatically after the monthly allotment is used up — packs with an expiry first — and the remaining balance shown includes them.

​

Organization settings

Organization owners and admins can manage the whole organization from “Organization settings” in the Settings screen (workspace list, members, connector / tool access controls, Shared assets for agents and skills shared org-wide, workspace auto-creation, usage, run history, operation logs, and more). The “Operation Logs” section lists each operation’s before/after values under “Changes” and includes them in its CSV export. The Settings section includes a “Sign-in & home notice” card for organization-specific usage rules or policies. Turn on “Show the notice,” enter up to 2,000 characters, and save; line breaks are preserved. A bare http:// or https:// URL becomes a link, as does [label](https://example.com); other markup is shown as plain text. The notice appears below the greeting on the home screen (it is shown on the sign-in page as well only in deployments set up for a single organization, such as on-premises installs). Turning the switch off hides it without deleting the saved text, and an empty text stays hidden even if the switch is on. The organization’s “Usage” section is a self-serve usage report. Switch the period between “This month,” “Last month,” and “Last 30 days” (days are counted in Japan Standard Time), and switch the view between “Overview,” “By workspace,” and “By member.” Clicking a workspace row drills into that workspace’s daily detail and its per-chat, per-agent, and per-model totals. The per-chat view shows chat titles so heavy consumption can be audited — never chat contents — and an organization can have titles hidden by policy, in which case rows read “Chat with <agent>” instead.

​

Danger zone

• Leave workspace — until you are invited again, you lose all access to this workspace’s chats, agents, and knowledge. The sole owner cannot leave
• Delete workspace — every chat, agent, skill, knowledge source, file, and connector inside is deleted. You must type the workspace name to confirm

​

Creating and switching workspaces

• The workspace switcher at the top of the sidebar is organized organization first: the menu shows the current organization, a search box, and that organization’s workspaces, with “Create workspace,” “Workspace settings,” and “Invite members” (owners) at the bottom
• To change organizations, open the organization row’s submenu and pick one — you land on the workspace you last used in that organization. Organization owners and admins also get a gear shortcut to Organization settings on the organization row. When you belong to more than one organization, that submenu carries its own “Search organizations…” box (filter by name or slug; Enter switches to the first match)
• In the creation dialog, “Add all organization members” loads the organization’s member directory into a list you can prune (filter by name or email, remove individual rows). Everyone left on the list is added when the workspace is created — members who have never signed in join automatically on their first sign-in. This is a one-time addition, not a continuous sync with the organization
• An organization can have an organization-wide shared workspace, named after the organization, that every organization member joins automatically — on their first sign-in, or the next time they open the app once the workspace exists. The first member to arrive becomes its owner, everyone after that joins as a member. Someone removed from it (or who left) is not added back automatically; an owner adds them again from the Members tab
• SSO sessions may be locked to the organization you signed in with. In that case, sign out first, then switch