00:00:04:05 - 00:00:29:17
Hi everyone and welcome to this SwiftFox Masterclass. Today we're focusing on building your own Action Center. Action centres are one of the most powerful parts of SwiftFox, also one of the most flexible, which means they can be easy to overlook or under use. This session isn't about running through every setting or option. Instead, we're going to look at how action centres come together and practice how to build them in a way that supports real day to day work.

00:00:29:21 - 00:00:40:00
By the end of this masterclass, you should have a clear understanding of what action centres are designed to do, how to structure them so they make sense for your teams, and how to build one that people actually want to use

00:00:40:04 - 00:01:08:31
At their core, action centres alive operational views into your SwiftFox database. They sit somewhere between a report and a workspace. Unlike static reports, action centres are always live. They’re searchable, but the real value isn't the table itself. The value is that action centres let you bring related work together into one place.filterable and sortable. They can be exported and in many cases data can be edited directly from the table.

00:01:08:35 - 00:01:34:02
Instead of jumping between profiles, running exports, or relying on spreadsheets, you can create focused views for case management, finance workflows, reviewing form submissions, tracking CPD and goals, managing lists and directories, and auditing posts and interactions. That's why action centres appear in the left hand navigation. They're designed to be places your team works from, not screens. I occasionally visit.

00:01:34:06 - 00:02:07:44
Before creating an action centre, the first thing to think about is where it belongs. Action centres are organised into areas which appear in the left side bar, and sections which group related action centres within that area. This structure is important because it reflects ownership. For example, finance related action centres live together. Membership related action centres live together. Operational workflows live together. When an action centre lives in the right area, it immediately makes sense to the people using it. It feels intentional, not bolted on.

00:02:07:48 - 00:02:28:13
Once you know where the Action Center belongs, the next decision is the type. A simple way to think about this is based on how the work starts. If the stocks from a list of people or organisations. A list builder action centre is usually the right fit, if it's finance related, one of the financial action centres will be appropriate.

00:02:28:17 - 00:02:48:08
If it's about reviewing submissions, form responses is usually the best option. If it's compliance or CPD goals or goal activities are a better match. If it's interaction based posts or cases tend to work best. You don't need the perfect type. You need the one that best reflects how the work begins.

00:02:48:12 - 00:03:01:45
Once the type is understood and the basics are setup, the focus shifts to usability. This is where it really starts to earn its place. In this next stage, you're making decisions about how you want this action centre to be used.

00:03:01:49 - 00:03:24:06
For form and list builder types. This means which columns are visible, the order those columns appear in, and which fields should be directly editable in the table. For financial types, this means what default filters should apply to segment the data to keep it focused. With columns, this starts by removing any defaults that aren't essential to your workflow.

00:03:24:10 - 00:03:31:33
A good rule of thumb here is if a column doesn't support a decision or an action, it probably doesn't need to be visible.

00:03:31:37 - 00:03:55:01
From there you can reorder columns so the most important information appears first. This small change alone can dramatically improve how usable the Action Center feels. You want the table to guide your team. For types that support editing. You can choose which fields should be editable directly in the table. This allows teams to make quick updates without opening individual profiles.

00:03:55:05 - 00:04:00:44
Finally, default filters control what users see the moment they open the action centre.

00:04:00:48 - 00:04:19:00
Instead of starting with everything. You can narrow the view to what actually matters day to day, such as recent records, outstanding items, or specific statuses. When all of this comes together, you're no longer looking at a generic table. You're designing a workspace that's ready to use the moment someone opens it.

00:04:19:04 - 00:04:46:03
Once the table is shaped, the final step is permissions, and this should be part of the design. Not an afterthought. All action centres use the standard permissions options. Here you can configure access to users or user groups and choose between Full Access, View and Edit Access or View only access. This is a good point to pause and ask who needs to take action here and who just needs visibility.

00:04:46:07 - 00:05:02:11
For example, a small operational team might have added access, while leadership just needs a read only view. Because action centres can allow in table editing. Being deliberate about permissions helps maintain clean data while still giving teams the flexibility they need

00:05:02:15 - 00:05:25:34
Before we wrap up, I'd like to leave you with an example of where you might use this in a way that you hadn't initially considered. One of the best examples of that with action centres is when you start designing them to work together. A lot of users start by thinking, I need an action centre that shows me X. That's a good starting point. But in many cases, what you're managing is a process that moves through stages.

00:05:25:38 - 00:05:53:00
A simple example is a sales or engagement pipeline. Instead of one action centre, you might create a small set of action centres, all based on the same underlying data and all filtered on the same custom field, such as a stage field. Each action centre represents a different stage. Stage one, stage two, stage three, and so on. The key part is making that stage field visible in the table and marking it as editable.

00:05:53:04 - 00:06:04:41
Once you do that, moving forward becomes incredibly simple. You update the value directly in the table, and the moment that happens, the record drops out of one action centre and appears in the next.

00:06:04:45 - 00:06:29:09
You're not opening individual profiles. You're not running bulk updates. You're just working in the view. And while sales and engagement pipelines are an easy example, this pattern works just as well for things like membership approvals, case progression, or internal review workflows. The real takeaway here isn't the specific example. It's the way of thinking. Action centres don't have to stand alone.

00:06:29:19 - 00:06:35:27
When you design them as a connected set, they can reflect an entire journey, not just a snapshot of data.

00:06:35:31 - 00:07:03:29
So to wrap things up, action centres are about making SwiftFox work the way your organisation works. They give you a way to pull the right information together. Put it in front of the right people and make it easy to take action without jumping all over the system. If you're just getting started, don't feel like you need to build everything at once. Pick one workflow, build one action centre around it and see how your team uses it. From there, it becomes much easier to refine and expand.

00:07:03:39 - 00:07:08:16
Thanks for spending the time with us today, and we'll see you in the next Masterclass.

‍