Hello everyone,
I'm trying to discover whether I can use an existing module as is, modify one, or whether I need to start from scratch. A company I'm doing some work for is using several Drupal sites for their Intranets, documentation, and even trouble tracking. Now, they'd like to unleash one of these sites on a customer [ insert appropriate smiley here ].
Each customer has potentially several hundred vendors. Each vendor, aside from being able to access public documents on the intranet, needs to be able to view a small handful of reports, updated daily. Given that there will be potentially hundreds of vendors on a site, it would be great if these documents could be keyed by the user's Drupal ID. They log in, see a half a dozen links to consistently named nodes (or records), but no one else can, except the 'super-vendor' who can see all of their vendors' records as well.
Like this :
Vendor1 can see vendor1-report1, vendor1-report2, vendor1-report3
Vendor 2 can see vendor2-report2, vendor2-report2, vendor3-report3
. . . you get the idea.
SuperVendor1 can see everything Vendor1 and Vendor2 can see.
Issues I see are as follows.
- The reports would likely have to be inserted into the appropriate node via a command line SQL update (this part pretty much has to happen in the background).
- I'm guessing the reports would have to be stored with the username as part of the key.