Client portal user guide

This guide is for clients who have accepted a proposal and signed an agreement with an organisation in the ecosystem, from the owner who signed to the colleague who only needs to upload a file.

Before the portal opens, your project manager books review meetings with you, progress updates are sent by the delivery team, decisions made in meetings are recorded, and the files you send are attached to your project. When the portal opens, that history is already in place.

The portal never shows another client's information or the delivery organisation's internal notes, costs, rates, salaries or margins. If you are also a learner or member, you use one account; moving between organisations is an explicit switch.

There is no public sign-up. When your agreement is active and the project is created, the people named in your agreement receive an invitation by email.

Paying an invoice, accepting a quotation or signing a document are planned to need stronger verification; turn on two-step verification when it is available. Your first screen shows the kickoff meeting, the first milestone, the delivery team and your onboarding tasks, each with a due date.

The dashboard shows only what your role allows. You can choose a regular digest instead of signing in every day; urgent items are still sent as they happen.

In practice. Look at "Waiting for you" first. If it is empty, nothing on your engagement is held up by you.

A colleague who leaves should be removed straight away; removal ends access at once, and past actions stay on the record under their name. Every approval, rejection, comment, upload, payment and change of role is recorded.

If you bought a package of sessions, the portal shows your allowance. A session is counted when it is booked and returned if it is cancelled within the cancellation policy.

An approval is your formal decision on a deliverable or milestone, recorded with the person, the time, the version approved and any comment.

If you want something that was not in the agreement, use the request centre rather than a change request on the deliverable.

Proposals, agreements, change requests, deliverables, shared files, meeting summaries, invoices and receipts are kept in one place. Each uploaded file is checked for harmful content before anyone can open it. A revised document is added beside the old one, never replacing it, so you can always see which version was approved.

Electronic signature inside the portal is planned. Until then, documents are signed in the way agreed with your project manager. A signature recorded on the platform is a recorded acceptance, not a qualified electronic signature.

Booking a meeting is planned for the first public release. Every booking is confirmed with a calendar entry and the details for joining, and you receive reminders. You can reschedule or cancel within the notice period in your agreement.

Your first meeting is the kickoff: scope, timeline, how you will hear from the team, who decides what, and how success will be measured. Summaries, decisions and actions are recorded when the team marks them visible to you; the team's working notes stay internal.

Say what you need, why, by when, and what "done" looks like. If the request is outside the agreed scope, it becomes a change request with a quotation showing the cost and the effect on the timeline. Only the client owner can accept a quotation.

In practice. Send one request per need.

Invoices are issued by the organisation named in your agreement, under its own legal name and numbering, on the schedule your agreement sets. The billing area is visible to the client owner and the finance contact.

Payment is made through a licensed payment provider; your card or bank details are never stored by MominSheikh.com. Refunds are decided by a person in the finance team, never automatically. Raise a query on an invoice before its due date.

Keep conversations about a deliverable, task or request on that item. Conversations on personal messaging apps are not copied into the portal; ask for anything that matters to be confirmed in the portal.

If an action fails, the message gives a reference; quote it in your support request. Complaints are acknowledged in writing and looked into by someone other than the person they are about.

You choose straight away, a digest, or only in the portal for most notifications.

Your information is visible to your delivery team to the extent they need it, and to no other client. Invoices, signed agreements and approval records must be kept for set periods for tax and legal reasons. The portal is designed to meet WCAG 2.2 AA.

Nothing is published about your project without your written permission. A closed engagement is recorded as closed, not deleted; how long a closed workspace stays open to you is [to be set in the Records Retention Schedule]. Download the final deliverables, the signed acceptance and your receipts before it closes.