Teams, Webhooks, and MCP

We have a big release today! 3 large features have been added to the app, along with some smaller fixes and improvements. Let's dive into the big stuff.

🧑‍🤝‍🧑 What are Teams?

Teams are a new and better way to manage large amounts of users as groups. These groups can have configurable access to workspaces, so you can fine tune a set of users access to multiple workspaces, or quickly give or remove access from large sets of content in a few clicks.

How do I migrate my account to teams?

In your Account Settings -> Members page, you'll see a new button, Enable Team Based Permissions.

Mudstack will migrate your current account and workspace roles to the new teams system. We'll automatically create teams based on workspaces & workspace access.

Once migrated, you'll see a new page in account settings called Teams where you can edit the newly created teams.

Check out everything else you can do with teams here

🕸️ Webhooks is now available!

You can now create and manage your own workspaces within the application. You manage your webhooks in the Workspace Settings -> Webhooks page.

To get started with Webhooks...

• Create your webhook in the app and provide us a destination URL & headers of where you would like the events to go.
• Filter specific events sent through the webhook.
• Configure your destination to accept the payloads and transform the data. You can use intermediary apps like Zapier, or internal automation tools, like Jira’s automation tool.
• You can combine a webhook with API calls in the automation tools to enrich the webhook payloads with more relevant data.
• Test and go live!

For more info on best practices and some examples for webhook uses, check out our documentation on how to get webhooks set up in your workspaces.

Send us a message if you want us to track any other events from Mudstack!

💽 Our MCP Server is live!

You can now use LLMs to talk with Mudstack's cloud API. The access is based on your user permissions. Our documentation has instructions on how to set this up with different LLMs.

If you want us to add more tools to our MCP, let us know, here is what we currently support!

😎 What else is new?

• You can now share Push history URLs with other people.
• Updated some UX on setting a workspace location on a new workspace
• Added a new button to completely clear local database information via Help -> Troubleshoot -> Refresh Database. You will need to log in and remap content again after doing it.
• Searching and filtering in the push history will be retained when leaving the page

🪲 Bug fixes

• Cutting and pasting to the root folder on the web app wouldn't succeed
• Filtering by favorites in the web app wouldn't filter properly
• Libraries wouldn't display correctly in conflicts
• Selecting a filter, then clicking outside of a filter on the push history page above a line item would select that line item
• Library Thumbnail does not update when new thumbnail is added
• Adding and updating an attachment in the attachments tab wouldn't refresh the data correctly
• Force new files to map to existing last soft deleted files
• Fix sync commit versions missing from assets pushes, completed push records causing conflicts, and push records not being cleaned up after completion
• Only discard push records if pull completes, this should stop discards entering a bad state
• File path would extend outside the conflict columns
• Preview wasn't working on some .mp4 and .mov files