We are currently validating if power pages fit the needs of our customer. Here are some processes which power pages should be able to handle:
- One view for employees and one for external associations
- two different user interfaces with different layouts
- Queue registrations for approval of employees
- every registration from an external user needs to be validated before they can see the content of the website
- Registration form with categories containing authorization roles
- Upload of document necessary for approval (validation of the federation)
- Admin of a federation registers and can create additional users with limited permissions
- every external organisation has one admin which submits the registration. that admin should be able to register users of that organization. but the users only have restricted rights.
- In case of approval or rejection, the admin of the association receives a message with reason in case of rejection
- Can add a kanban dashboard for application display
- Drag and drop would be desired
- Deposit of projects on which external organisations can apply
- Application form with table function like excel with sum
- Project can have different status (Draft, Published, Inactive)
- A project can have sub projects where you can apply to as well
- Allow to manage releases for projects. Not all associations should be able to view all projects.
I would appreciate every help. I already looked through the documentation from microsoft regarding power pages, but wasn't able to validate those processes.
Thanks

Report
All responses (
Answers (