3 Items
#36 – Evolve Your Event Management
Steffen Burzlaff
Hey hey hey, this is your Weekly Dose of Confluence with the latest and most important Confluence news in 5 minutes. If you were forwarded this message, you can subscribe to the free weekly newsletter here.
This time, we’re bringing you a helpful example by showcasing how Confluence databases can be used for event management. Plus, learn about two updates: embeddable manual triggers for Confluence automation and bulk status changes.
Let's dive in!
Manage Your Events with Databases
In last week’s newsletter, we talked about using Confluence databases for directory management. Now it’s time for another use case: event management. Managing events can be a complex task involving numerous components like sponsorships, exhibitors, speakers, and session submissions.
By using databases in Confluence, you can efficiently manage various aspects of events by ensuring all information is organized and easily accessible. Our favorite part is the convenience aspect, since these databases are built into Confluence. You can work within pages alongside your event information. Plus, as an event manager, the ability to share these databases with your team will save you so much time in answering questions about when, where, who, and what is going on.
Creating and Structuring Your Databases
With so much information to keep track of, it’s great to have a database for each topic. For example, you can create one for the speakers, one for events, and one for sessions. In each of these databases, to keep entries organized, you can utilize different field types like simple text, dates, and multi-selects. For the sessions database, we’d include the session title that links to its main page, the date/time, as well as database entry links for the conference location and the speaker, which then link to other databases.
To accompany your sessions database, we recommend that you have a main page for each individual event session, and use a database Smart Link to display the relevant database at the top of that page. The purpose of the session page is to go more into detail and also be a place where your team can collaborate on that topic. Then, if you need to adjust the database entry from the main session page, all the changes are reflected simultaneously in the database on each page it’s embedded on.
This is just one of the five use cases we’re sharing with you over the next few weeks. Confluence databases offers many more possibilities.
Check out our video below to learn more about event management with Confluence databases!
Simplicity Now Embedded
Atlassian has introduced embeddable manual triggers for Confluence automation, enabling admins to embed manual triggers in other platforms such as email, Slack, and Jira. This nifty feature makes task delegation a breeze. Manual triggers can now be placed where users are, such as directly in an email. You can click and complete the action without needing to open a new page to find a status, label, or trigger.
Bulk Status Changes
Say goodbye to individually changing the status of your items, and wave hello to bulk changes! For Premium and Enterprise users, you can now change or remove the status for tons of items all in one go. Head to the community article to see exactly how to do this.
Overview Pages and Databases
Navigating numerous Confluence pages can be daunting, but overview pages make it easier to manage large amounts of content by providing a high-level view of related pages. We recommend using the page properties macro to display key data from multiple pages, and further enhance it with Confluence databases. Learn more in our best practice article!
