TIBCO’s tibbr New External Communities Empower Greater Collaboration With Partners, Customers, and More—For Free
Blog: The Tibco Blog
Here’s a question I’ve been getting more and more recently:
What’s the best way to build rich collaboration with our internal employees and members, and also securely and simply include external parties (customers, prospects, partners, vendors, consultants, etc) when necessary? And inexpensively too, please.
Fortunately, answering that is just as easy as setting up the solution in tibbr—and doesn’t cost anything for tibbr customers. If you use tibbr hosted in the cloud as your collaboration platform for internal collaboration, your organization is eligible to have as many external communities as you’d like, and as many users on each external community, too!
You want to have a private partner community that includes all your partners so you can communicate with all of them in one place. That’s easy! A specific external tibbr instance for all of your tier 1 suppliers? Yes, that too. What about an external tibbr instance for all of the attendees at your user conference or trade show attendees? Yes, no problem there either. All of these and many more scenarios are easy to setup when you have tibbr as your hosted collaboration platform.
What are your options for setting up the communities?
Under the hood is a sophisticated external community engine with many options for the varied scenarios unique to your organization’s needs. tibbr realizes you want to be able to have self-service with these external communities, so tibbr supports standard communities and user communities:
- Standard communities are other tibbr instances that are run by your organization’s partners, customers, suppliers, or resellers and that are made available by your tibbr administrator. No need to contact tibbr to setup the instance, you can do it yourself from the GUI.
- User communities are tibbr instances created by permitted users (your organization can decide who should have this permission). This way, power users themselves can create communities, without even needing to contact the tibbr administrator within their organization. The user who creates the user community is that specific external community’s tibbr administrator, and can invite other users to join. These users can create communities, such as those run by your organization’s partners, customers, suppliers, or resellers in other tibbr instances so that your users can access the posts there. In addition, you can edit community properties or grant access to all users or to only those you specify.
How does it work?
Your tibbr administrators decide who should have the ability to create external communities. Those users can then create their community with just a couple clicks. Inviting users (from any email domain) is just a few more clicks. The external users in your external community do not have access to your private internal tibbr—only to the external communities they’ve been invited to. Your internal employees that are in multiple communities have the ability to see and access the posts, notifications, etc., across all their communities, all in one simple GUI. Your internal employees can even share messages on the external community back to the internal tibbr instance, to point out specific opportunities or questions that deserve attention. Here’s what set up looks like:
tibbr provides the tools that enable you to take action and harness the collaborative power of your organization. With tibbr’s external community features, that now extends to the organizations you work closely with. If you’d like to take action in getting your team collaborating—both internally and externally—please contact tibbr at firstname.lastname@example.org.