Skip to main content

Managing Swif's Desktop App UI and Company Resources

Updated today

This article explains how workspace admins can configure organization‑wide settings and company resources for the Swif desktop app and browser extension from the Swif web app.


Who can use this feature?

Only workspace / organization admins can view and edit Workspace settings and company resources.

Non‑admin users:

  • Can’t see or edit the Resources configuration in Settings → Workspace.

  • Can’t add, edit, or delete resources.


1. Accessing Workspace settings

  1. Sign in to the Swif web app as a workspace admin.

  2. In the left navigation, go to Settings.

  3. In the Settings navigation, click Workspace.

You should see:

  • A modernized Settings navigation (legacy tabs removed, per the new “Workspace 1.0.0” design).

  • A Workspace page that includes:

    • Workspace‑level customization controls for the desktop app and browser extension.

    • A Resources section where you manage company links and content.

If you still see older “General” tabs containing desktop‑app controls, contact your Swif admin or support—your environment may not be on the latest version yet.


2. Understanding Company Resources

Company resources are curated links and content your organization wants employees to see in the Swif desktop app and browser extension—for example:

  • Employee handbook

  • Internal wiki / knowledge base

  • IT support portal

  • HR portal or benefits site

  • Onboarding resources

Admins can:

  • Add new resources (with icon, title, URL, optional description).

  • Edit existing resources.

  • Delete resources.

  • Reorder resources (if sorting controls are present in your UI).

These resources are scoped per organization/tenant:

  • Org A sees only Org A’s resources.

  • Org B sees only Org B’s resources.

  • There is no cross‑org sharing or leakage of resource data.


3. Viewing the Resources section

To open the Resources configuration:

  1. In the Swif web app, go to Settings → Workspace.

  2. Scroll to the Resources area.

You’ll see one of two states:

Empty state (no resources yet)

If your org has no configured resources:

  • You’ll see an empty state message such as “No company resources yet.”

  • An Add Resource button or call‑to‑action (CTA) is visible and enabled.

  • No placeholder/ghost rows are shown.

Populated state (existing resources)

If resources are already configured:

  • You’ll see a table/list of resources, each with:

    • Icon (default, type‑based, or custom).

    • Title.

    • URL.

    • Optional description (if your design includes it).

  • Row actions such as Edit and Delete/Remove are available.


4. Adding a new resource

  1. Go to Settings → Workspace → Resources.

  2. Click Add Resource.

You’ll see a form similar to the “Add Resource 1.1.0” design, which includes:

  • Icon

    • Choose from default icons (for example, handbook/wiki/support) or upload a custom icon, depending on your plan.

  • Title (required)

    • Clear, human‑readable name, e.g. “Employee Handbook”.

  • URL (required)

    • The link employees will be taken to when they click the resource (for example, your wiki or support portal).

  • Description (optional, if shown in your design)

    • Short description or guidance about what the resource is for.

Validation and saving

  • Title and URL are required:

    • If left blank, the form shows inline validation errors.

    • The Save action is blocked or disabled until required fields are valid.

  • The URL field enforces basic URL format on the frontend:

    • Clearly invalid strings (e.g. “abc”, “123”) are rejected.

    • Use a full URL with protocol, e.g. https://….

  • When you click Save:

    • The form calls the Resources API (create).

    • The Save button shows a loading/disabled state while the request is in progress.

    • On success:

      • The form closes.

      • The Resources list refreshes and shows the new resource row.

If an error occurs (network issues, permission errors, etc.), you’ll see an error message and the form will remain open so you can retry or adjust values.


5. Editing an existing resource

  1. Go to Settings → Workspace → Resources.

  2. Find the resource you want to modify.

  3. Click Edit on that row.

The edit form:

  • Opens pre‑populated with the existing icon, title, URL, and description.

  • Applies the same validation rules as Add:

    • Title and URL remain required.

    • URL format checks still apply.

Make your changes, then click Save:

  • The app calls the update endpoint.

  • While saving, you’ll see a loading/disabled state on the Save button.

  • On success:

    • The dialog closes.

    • The row in the list updates immediately.

    • Re‑opening Edit shows the updated data.

If the update fails, an error is displayed and your previously entered values are preserved so you can adjust and retry.


6. Deleting a resource

  1. Go to Settings → Workspace → Resources.

  2. Locate the resource you want to remove.

  3. Click Delete or Remove on that row.

You’ll see a confirmation dialog explaining that:

  • The resource will no longer be shown in the Swif desktop app (and any other surfaces that consume this configuration).

Confirm to proceed:

  • The app calls the delete endpoint.

  • On success:

    • The row is removed from the list.

    • If that was the last resource, the view returns to the empty state with the Add Resource CTA.

If the delete fails (e.g., network issue), an error message appears and the resource remains in the list.


7. How resources appear in the desktop app (including the login / welcome screen)

Once configured, these resources are used by the Swif desktop app and, where applicable, the browser extension.

A few notes from the implementation:

  • The desktop app (and possibly the login/welcome screen) reads from the same Resources configuration.

  • A special resource may be used to power the welcome/intro experience on the login page:

    • Internally, this resource is marked via a title prefix such as __LOGIN_PAGE__ so the desktop app can treat it as the “welcome” block rather than a regular resource link.

    • Fields may be mapped as:

      • Title (with __LOGIN_PAGE__ prefix) → internal identifier.

      • Description → “Welcome message” copy on the login screen.

      • Icon URL → image/media displayed on the welcome card.

      • URL → optional video or deeper content link.

You don’t need to manage the __LOGIN_PAGE__ prefix directly unless instructed by Swif support or your implementation team; in most cases, you’ll simply configure the welcome content through the same Add/Edit resource UI.


8. Permissions and multi‑tenant behavior

  • Only workspace admins can:

    • Access Settings → Workspace → Resources.

    • Add, edit, or delete resources.

  • Non‑admin users:

    • Cannot access the Resources configuration page.

    • May see the resulting resources only where the product surfaces them (e.g., in the desktop app UI), without having any configuration controls.

  • Resource data is strictly tenant‑scoped:

    • If you manage multiple orgs/tenants, you must configure resources separately for each.

    • Changes made in Org A have no effect on Org B.


9. Troubleshooting

I don’t see the Workspace tab.

  • Make sure you:

    • Are logged in as an admin.

    • Are using the latest version of the web app.

  • If it’s still missing, your org may not have this feature rolled out. Contact Swif support with your org ID and a link to your environment.

Resources are not appearing in the desktop app.

  • Confirm that at least one resource is configured and saved.

  • Check that you’re logged in to the same org in both the web app and the desktop app.

  • If your org uses a custom welcome resource for the login screen, verify that its title/fields match the configuration recommended by Swif.

I still see desktop app settings under General.

  • You might be on an older build, or your browser has a stale cached bundle.

    • Hard‑refresh the page or try an incognito/private window.

  • If the issue persists, contact Swif support and mention that your General tab is still showing legacy desktop app controls that should be under Workspace.

Did this answer your question?