Portal Sync

Connect once, keep working

Alshitask is useful on its own. Connect it to Alshival.Ai when you want your local app or server instance to participate in a shared workspace.

Connect your account

1. Open Settings and choose the Alshival.Ai account connection.
2. Complete sign-in and consent in your browser with your own portal account.
3. Return to the app. Authorized workspaces appear in the workspace switcher and synchronize in the background.

The server preview also has an owner password. That password opens your server instance; portal OAuth separately authorizes access to your shared workspaces. For a server accessed through an SSH tunnel, keep the tunnel open through the callback.

Local means local until you publish

Connecting does not automatically upload local boards. Use Publish local boards when you choose to move a board into an authorized portal workspace. Review the destination before publishing.

Hosted team collaboration is the paid membership benefit. Standalone local use does not require a subscription. Membership, plan availability, and workspace permissions still govern shared actions. Billing and administration remain in the portal.

What happens offline?

The desktop app can save local work without a network connection. A browser needs a connection to its server; if that server loses portal connectivity, its local workspace remains available to browsers that can still reach it.

Eligible shared edits queue for sync. Overlapping edits become conflicts to review, and permission-rejected edits remain visible as drafts. A disconnected or incomplete sync is not permission to delete local work. Resource-log forwarding is configured separately; connecting a workspace does not automatically forward all its logs.

Will I have to keep signing in?

Connected instances refresh portal credentials automatically. They use the shared rolling 45-day refresh window and interrupted-refresh recovery. Keep the instance running and its credential storage available for unattended use.

A revoked connection, removed permission, or absence beyond the accepted refresh window can require sign-in again. The goal is routine renewal without repeated prompts, while preserving your ability to revoke access. Browser owner sessions and MCP bearer tokens have their own lifetimes; see server mode.

If a workspace needs attention

Check its last-sync time and error in Settings. Confirm the server or desktop service is running and can reach the portal. Review drafts and conflicts before retrying. Avoid signing out as a first troubleshooting step; it can interrupt a connection that only needs time to recover.

For Cross-site request denied after portal consent in an older server preview, update to the corrected preview, then reopen the configured app URL. The account may already be connected. For Connection refused, first confirm the server is running on the port in the URL. More checks are in Troubleshooting.

---

Published from the versioned Alshival documentation source. Edit the source rather than this generated page.