Task 8 – Add/invite users, accounts, and permissions.
So far you’ve documented your “why”. You mapped it to Communifire’s features. And you populated the site with content and made it visually stunning.
Now it’s time to start adding users and team members. Just as you wouldn’t let anyone walk into HR and start rifling through employee files, make sure users have access to the information they need. While also restricting access to discussions and content they don’t.
Remember, setting access permissions isn’t just about keeping users out of areas they don’t belong. It’s also about keeping their experience clean and uncluttered. They don’t want information they don’t need clogging up their activity stream. Setting user access privileges keeps things neat and organized.
Communifire’s user admin and permissions is intuitive. But if you have questions, our support community can be a great resource. There’s plenty of advice, how-to’s, and best practices available to help you learn from the success of others. That’s one of the best parts of working with Communifire: you never have to do it alone. We encourage you to tap into the vast and valuable experiences of intranet site admins who have “been there, done that” and are eager to help you learn from their experience.
Goal: Add users and grow adoption by giving them access to the vital content they need.
More information: Learn how to setup User Roles and Permissions.
A word about custom intranet development and integrations.
We’re often asked about integrations. The topic deserves a small space in this “getting started” guide.
Sometimes integrations with other platforms make sense. For example, using Active Directory (AD) integration to synchronize user account data between systems. Other times, integrations might take more effort than what you need. Rather than direct integration, it might be easier to add a hyperlink to lead people to a time tracking or payroll system.
Let’s start by asking the most important question: why? What is the purpose for integrating another system or platform? Is it just a novelty? Or does the integration actually add value? If there’s a benefit to integration, such as eliminating redundancy, increasing efficiency, or reducing errors and data discrepancy, then an integration makes sense. But, if you can’t find value, a simple link from Communifire to other system(s) is enough.
If integration does make sense, start by documenting what that integration looks like and how the systems should behave together. Will it be a one-way push of data from one system to another? Or, is a two-way stream of data required to synchronize back and forth between systems? Do these pushes happen instantly or on a timed cycle? Exactly which data fields must transfer? What is the workflow?
While integration work is outside the scope of this guide, it is well within the capabilities of the Communifire platform. For more information about integrating Communifire with your existing technology stack, please visit the REST API guides to learn how to work with this tool.