I am needing to build a custom portal for very specific needs in my client. They work with dozens of outside contractors and so the basic idea is that the portal will have separate login accounts for each person, including the CEO, accountant, IT, etc. Within each person's "home", they will have access to documents specific to them, as well as any documents, training materials, policies and contracts specific to their contract level or group.
The portal will also allow them to submit forms or other requests, tasks or jobs. It should allow them to track progress, receive feedback, leave feeback, communicate with other contractors, and allow promotion to higher contract levels.

There are a lot of specific needs as far as user groups. For example, one user (an employee) is responsible for uploading specific documents to specific contractors, and yet they don't need any access or abilities to do anything else. Some contracts at higher levels may get certain access to video or other training or materials and have different finance data.

Everybody from top to bottom should be able to get reports on things like how many jobs they performed or get a listing of client data or pull down the current calendar (updated by another employee). They will receive email notifications when files change, new files added, tasks added, or comments left on their jobs and tasks.

With all these specific needs, I'm not finding that generic intranet/portal tools are allowing me to customize and build the pages and access that I need. Take something like Sharepoint, it's mainly for document management, but we need fine grained control over each user account and access level, plus add other sorts of communication, forms processing, report generating and custom data.
I've tried general intranet tools like Podio, Mangospring, Yammer, Huddle, Clinked, Basecamp etc. For one thing, we don't want to have to "buy" user accounts for all the contractors, and none of them really let me build my OWN pages, you either use a group, or chat, or wiki, or document collaboration, or tasks, projects, calendar, "updates" or "sharing", but really our needs go beyond just communicating in "posts" and "projects". We need more automation than this.

It seems like we need a totally custom solution that is purpose-built for the organization. However, I don't want to reinvent the wheel. I'd like to start with SOME kind of framework that doesn't lock me into their mold. I want some basic bits like database access, authentication, user roles and abilities, security, templates, file management already built in. Maybe that's not possible?

I'm not sure exactly what to look at. A CMS? A framework vis a vis Phalcon or Laravel? Or just install Composer with PHP and start chucking modules into a totally custom project?

Any ideas?

Dani AI

Generated

A pragmatic route is to assemble a modular portal instead of building every piece from scratch or shoehorning everything into a closed SaaS. ’s list (fine‑grained ACLs, tiered materials, forms, task tracking, notifications, reporting) is large and aligns with ’s timeline warning that a polished, secure intranet is measured in months. Since this thread dates to 2014, modern hosted services and libraries can cut plumbing time, but the ACL model and workflow design still drive most of the work. ’ and ’ pointers toward document platforms or CRMs surface useful building blocks, yet neither will likely cover custom workflows and reports out of the box.

Core components to treat as separate, testable pieces:

  • Authentication and RBAC (role/group/attribute rules plus an admin UI and audit logs).
  • Document store and metadata (versioning, per-file ACLs, searchable metadata, bulk import).
  • Workflow/forms engine (configurable forms, approval states, background job processing).
  • Task tracking and threaded comments (activity stream, ownership, status history).
  • Notifications and webhooks (batched email, in‑app alerts, external integrations).
  • Reporting/exports and audit reporting (scheduled exports, CSV/Excel, event logs).
  • Integration layer / API surface (calendar sync, finance systems, SSO).

Practical roadmap: define a role×feature matrix first and prove the ACL model with a small dataset. An MVP should implement auth+ACL, document upload/visibility, task submission, basic notifications and a simple report export. If content is mostly pages and documents, a flexible CMS can accelerate early delivery; if relationships and workflows are complex, use a modern framework and assemble mature libraries for permissioning, storage and queuing rather than reinventing them.

Operational cautions: design for backups and encryption at rest for sensitive finance files, build automated tests that assert role boundaries, and load-test file operations. A short PoC (6–12 weeks) will surface most unknowns and keep the larger estimate aligned with ’s projection.

Recommended Answers

All 3 Replies

Have you looked at Alfresco? It's based on the document sharing idea, a bit like sharepoint, but is quite customisable. It won't have everything you need immediately but it must tick a few boxes at least.

SugarCrm perhaps?

Member Avatar for Member #46692

To build that from scratch you're looking at about at least a half a year best, year realistically.

Codeigniter or laravel is capable, but it just gives you to php tools, you'll then have to work in a good html css framework like bootstrap.

You may find some solace in existing cms like sugarCRM but I wouldn't envy you having to reverse engineer that to get it working like you want!!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.