By Artem Korsakov ·
In short: Giving a partner CRM access works if the system lets you show them only the records and actions they need on your plan. A separate portal is justified when the partner has their own stable process: registering projects, documents, inviting colleagues. Choose by tracing the full path of one record and the maintenance cost of both options, testing them in a small pilot.
A partner portal helps partners submit contacts, register projects and see deal statuses, but some of these tasks can be covered by CRM access. Sometimes a role already available in your CRM solves the problem. In other cases, the internal interface and data model create more limitations than benefits.
Choose based on the partner’s working actions and acceptable visibility of information. An attractive separate screen does not justify development on its own, and having a CRM does not prove it can be safely opened to external users.
When to start with what the CRM can do
Check whether your current product lets you give a partner only the records and actions they need. For example, submitting a lead, adding a comment and seeing the manager’s decision. It is important to check permissions on your specific plan and in the version you use. The capabilities and licensing terms of different systems cannot be assumed to be the same.
The advantage of this route is fewer separate places to work. A manager and a partner can work with the same record if the system allows it. But setting up roles, training and maintenance still take time. Access that is “like an employee’s, just a bit less” without checking individual fields creates uncertainty.
Why a company needs a separate portal
A portal becomes justified when the partner needs a stable external process that differs from internal sales. For example, they register a project with attachments, receive a decision, see documents under their contract and invite colleagues. The internal CRM can then change without completely rebuilding the external scenario.
Suppose a hypothetical supplier works with installation companies. The partner specifies the site and the equipment, and the manager handles negotiations and procurement. The partner needs registration confirmation and a visible status. There is no need to show the manager’s interim notes, purchase prices or negotiations with other parties. A separate portal lets you define this boundary explicitly, but it requires correct data exchange. How to set up roles and permissions inside a portal is covered in the article about a company portal.
Compare the full path of a record
Take one project and trace it from creation to closure. Where are duplicate registrations checked? Who corrects a wrong site address? What will the partner see if the manager merges two records? Until the answers are agreed, arguing over which interface to choose is premature.
For the portal, describe separately which system holds the master version of each value. The partner can edit the description until the request is accepted, and then the manager fixes the terms. Two-way editing of the same field without rules creates conflict regardless of the tool chosen. Similar rules are needed for website leads; see the article “Website leads in a CRM”.
Calculate maintenance for both options
For the CRM option, check:
- the cost of external access;
- account management;
- plan limitations;
- partner training.
Do not apply the overall cost of the system to the new audience without checking the terms. The cost structure may change as the number of organizations grows.
A separate portal brings development, hosting, maintaining the data exchange and permission checks. A change in the internal process may require changes to the portal. In the estimate, it is useful to see the initial work and ongoing maintenance separately, so that initial savings do not hide later obligations.
Also check what happens when a partner leaves: who revokes access for their staff, what happens to open projects and which documents stay with your team. If the relationship resumes later, you need a clear procedure for restoring work. This scenario helps uncover hidden differences between an internal CRM account and a separate organization in an external portal.
Run a small working pilot
Give a partner representative a practice task without hints: register a project, find its status and fix a comment. Count the confusing steps and the times they had to turn to the manager. Speed on the first screen tells you little here. Use the same process in both options for comparison.
If the external scenario is already noticeably different, look at the trike_dev partner portal demo and compare it with what your system can do.
Частые вопросы ### Can we work in the CRM first and build a portal later?
Yes, if you keep clear identifiers for partners and projects, as well as access rules, from the start. Starting with an existing tool is reasonable when it handles the process without risky workarounds.