ABz B👹anaz
Grandfathered In 
This country is (now less of) a shitshow.
Posts: 1,989
|
Post by ABz B👹anaz on Sept 16, 2021 14:55:27 GMT -5
Hey all you IT or IT-adjacent peeps, Does anyone here have - or know someone who has - experience building websites with a database and file storage? My company's customer reports site is collapsing, and the guy who built it for us 7-8 years ago is nuts/useless, so I have been tasked with trying to find a replacement. Our new IT company is also soliciting quotes but I can recommend someone myself if they're comparable in price. This site needs to have: - A separate list of logins (username/password) for all of our customers.
- Storage of reports in PDF format for each customer, categorized by report type.
- A separate administrator login with the ability to manage these customer logins and reports, upload/modify/delete, etc.
Is this something anyone here could assist with? Send me a PM or reply here! |
|
|
|
Post by Powerthirteen on Sept 17, 2021 9:03:57 GMT -5
I gotta ask - are they opposed to just doing this as a repository in Sharepoint? Because this sounds pretty straightforward and not like something that needs a custom-built website.
|
|
ABz B👹anaz
Grandfathered In
This country is (now less of) a shitshow.
Posts: 1,989
|
Post by ABz B👹anaz on Sept 17, 2021 9:12:35 GMT -5
I gotta ask - are they opposed to just doing this as a repository in Sharepoint? Because this sounds pretty straightforward and not like something that needs a custom-built website. It's possible, but none of us (including me) are familiar with Sharepoint yet. The big concern is security. Having separate logins for each customer is absolutely required as they're hospitals and health systems. |
|
|
|
Post by Powerthirteen on Sept 17, 2021 9:31:22 GMT -5
I gotta ask - are they opposed to just doing this as a repository in Sharepoint? Because this sounds pretty straightforward and not like something that needs a custom-built website. It's possible, but none of us (including me) are familiar with Sharepoint yet. The big concern is security. Having separate logins for each customer is absolutely required as they're hospitals and health systems. What I would do would be to have a core Sharepoint library that has all the reports, that's accessible only to internal people, as well as a separate library for each client organization. Each file in the main library would have tag categories for Published/Unpublished and for what client organization it was for, and I'd set up a Power Automate flow so that when you tag a core library file with an organization it gets copied to that org's library. Files in each org's library would be secure and only accessible to admin-defined users who would have access to only their org's library. If your organization has Office 365 you're probably already paying for most or all of this functionality. I'm somewhat green at Sharepoint myself, but there are Sharepoint-experts-for-hire out there who could probably set a version of this up for you much more cheaply than having someone custom build it - plus you'd have free tech support from Microsoft, and in my experience they are *very* helpful once you get them on the phone about this kind of thing. |
|
ABz B👹anaz
Grandfathered In
This country is (now less of) a shitshow.
Posts: 1,989
|
Post by ABz B👹anaz on Sept 17, 2021 9:36:08 GMT -5
It's possible, but none of us (including me) are familiar with Sharepoint yet. The big concern is security. Having separate logins for each customer is absolutely required as they're hospitals and health systems. What I would do would be to have a core Sharepoint library that has all the reports, that's accessible only to internal people, as well as a separate library for each client organization. Each file in the main library would have tag categories for Published/Unpublished and for what client organization it was for, and I'd set up a Power Automate flow so that when you tag a core library file with an organization it gets copied to that org's library. Files in each org's library would be secure and only accessible to admin-defined users who would have access to only their org's library. If your organization has Office 365 you're probably already paying for most or all of this functionality. I'm somewhat green at Sharepoint myself, but there are Sharepoint-experts-for-hire out there who could probably set a version of this up for you much more cheaply than having someone custom build it - plus you'd have free tech support from Microsoft, and in my experience they are *very* helpful once you get them on the phone about this kind of thing. Okay, I'll look into this as well. The main concern for doing this would be how the clients accessed the system - if they all need their own Office 365 accounts, and would be accessing these files through those accounts, I don't think it would work for us because we would have no control over the logins themselves, only the files flagged for them. |
|
Baron von Costume
TI Forumite
Like an iron maiden made of pillows... the punishment is decadence!
Posts: 4,683 
|
Post by Baron von Costume on Sept 17, 2021 13:58:41 GMT -5
What I would do would be to have a core Sharepoint library that has all the reports, that's accessible only to internal people, as well as a separate library for each client organization. Each file in the main library would have tag categories for Published/Unpublished and for what client organization it was for, and I'd set up a Power Automate flow so that when you tag a core library file with an organization it gets copied to that org's library. Files in each org's library would be secure and only accessible to admin-defined users who would have access to only their org's library. If your organization has Office 365 you're probably already paying for most or all of this functionality. I'm somewhat green at Sharepoint myself, but there are Sharepoint-experts-for-hire out there who could probably set a version of this up for you much more cheaply than having someone custom build it - plus you'd have free tech support from Microsoft, and in my experience they are *very* helpful once you get them on the phone about this kind of thing. Okay, I'll look into this as well. The main concern for doing this would be how the clients accessed the system - if they all need their own Office 365 accounts, and would be accessing these files through those accounts, I don't think it would work for us because we would have no control over the logins themselves, only the files flagged for them. You'd have as much access to login perms for your files as you would if you were maintaining the logins themselves though and that's what really matters. Also makes actual account security/pw resets etc much less of an issue. |
|
