Navigation from the Alshival portal

This guide applies to Alshival-managed workspaces. Standalone Neural Labs navigation and configuration are unchanged.

The Alshival portal uses dedicated pages. Its workspace sidebar contains Board, Resources, Workspace Settings, and Neural Labs when available. The workspace switcher selects the workspace you are working in. Account Settings and Notifications have their own pages; staff administration remains permission-controlled.

Open Neural Labs to browse and manage general workspace files. The portal no longer has a document browser or a separate “Files in Neural Labs” export page. Authorized bookmarks to those former pages lead to the Neural Labs entry. If the workspace cannot launch Neural Labs, the portal shows an unavailable page with a link to Workspace Settings. Existing stored files are retained.

Open Workspace Settings → Agreements & billing for invoices, agreements, approvals, and related downloads. Internal workspaces do not have billing. Payment handoffs and authorized download links continue to work.

The Board keeps its timeline and editable notes. Tasks open in the task detail side panel; service tickets, deliverables, resources, and standalone note links open as pages. The floating Alshival assistant keeps its conversation while you navigate the portal.

These portal changes belong to the Alshival website repository. They do not change Neural Labs source, document storage, or external API/MCP contracts.

Portal assistant and Neural Labs chat

The floating Alshival assistant uses the normal private portal chat in every Alshival.ai workspace, including Pro and internal workspaces. Neural Labs runtime readiness and provider connections do not select the portal chat backend. Existing private portal conversations can continue normally.

Neural Labs shared channels and their history stay in Neural Labs. They are not imported into private portal conversations or listed in the portal widget. A browser remembering an old Labs chat opens a new private portal conversation. Open Neural Labs separately to access its chat and files.

Customer users share the configured workspace daily request allowance, resetting at 00:00 UTC. Defaults are Free 20, Go 100, Plus 500, and Pro 1,000. Staff chat is exempt in both client and internal workspaces; internal workspaces have no daily chat quota. Access checks, attachment limits, and per-conversation safeguards still apply. These rules belong to the Alshival portal, not standalone Neural Labs.

See the portal integration documentation.

Administrators can open Admin → Alshival to select separate client and staff models, including a custom model ID, and reasoning settings. Changed profiles are validated before activation and apply to subsequent turns. Configuration history is retained. SMS settings and sender checks have their own section; changing models does not require a Twilio check or alter chat quotas.

Both client and staff widgets use muted window controls. New chat and conversation history remain in the topbar; there is no Neural Labs button. Delete a conversation from its history row and confirm the action. Only its owner can delete it; deleting another conversation preserves the current draft.