Extranet launch checklist
This page is for the project lead who opens a portal to outside organizations. A mistake on an extranet is seen by people outside the company, so test more than you would for an intranet. Copy the list, assign a name to each line, and invite a first partner only when every block is ticked.
Contents
- Address and basics
- Separation
- Accounts
- Sign-in
- Files
- Ordering, if offered
- Mail and notifications
- Operations
- Pilot partner
- After launch
- Related pages
Address and basics
- To do: The portal's host name answers with HTTPS and the right siteaccess (Separate hosts and siteaccesses).
- To do:
SiteURLis the address partners use; mail links are built from it. - To do: The portal siteaccess has
RequireUserLogin=true; the public site hasfalse. - To do: The default administrator password has been changed (Default administrator password).
- To do: The administration has its own host name or network limits (Restricting the administration).
- To do: The portal design shows who is signed in and a sign-out link.
Separation
- To do: Test users exist for at least two partner organizations and two tiers.
- To do: Each test user sees its own area and not the other's, in pages, menus, search and downloads (Customer and partner areas, Testing the separation).
- To do: Logged out, the public host shows nothing of the portal; the portal host shows only the login page and the
pages in
AnonymousAccessList[]. - To do: No partner role shows Full access or Can change roles (Roles and policies, 1).
- To do:
user/loginin each role is limited to the right siteaccesses.
Accounts
- To do: The way accounts are created is decided and documented (Registration and account approval).
- To do: If registration is open:
DefaultUserPlacementpoints to an applicants group without rights. - To do: The "New user registered" mail reaches a monitored mailbox; approve and reject links tested.
- To do: If accounts are held until approved: one approved and one rejected in a test, with the workflow cronjob running.
- To do: CAPTCHA on the registration form (Spam protection for forms).
- To do: The registration form and the privacy notice say what data is kept and why (Consent and forms).
Sign-in
- To do: Password rules set (Two-factor and sign-in).
- To do:
MaxNumberOfFailedLoginset to a value other than0. - To do: Two-step sign-in decided: opt-in, required for all, or required for sensitive tiers (Two-step sign-in).
- To do: Password reset tested from the login page (Reset a user's password).
- To do: Support contact named for partners who are locked out.
Files
- To do: Every file area in the right section or partner subtree (Sharing files with partners).
- To do: A protected download tried as a user without access: refused.
- To do: Partner upload roles limited to the File class and the partner's folder; no remove.
- To do: Staff follow the upload folders.
Ordering, if offered
- To do:
shop/buyonly in the dealer role (Dealer and supplier portals). - To do: Discount groups and rules match the price policy.
- To do: VAT rules and currencies checked.
- To do: A full test order placed and processed in the Store tab (Store dashboard and order statuses).
Mail and notifications
- To do: Sender address and delivery tested to an outside mailbox (Mail delivery).
- To do: The e-mail preferences footer has the organization name and postal address (E-mail preferences: setting them up).
- To do: Notification run visible on Setup > Notification (Notifications: the administrator's guide).
Operations
- To do: Cronjobs scheduled, including the
frequentgroup (Cronjobs). - To do: Backups scheduled and one restore tested (Backups that restore).
- To do: Audit trail running:
./console exp:audit status(The audit trail). - To do: Monitoring of the portal address (Health checks and monitoring).
- To do: Update plan agreed (Upgrades without surprises).
Pilot partner
- To do: One friendly partner invited first.
- To do: The partner signs in, finds three named documents, uploads one file and (if offered) places a test order.
- To do: Feedback collected and fixed before more partners are invited.
After launch
- To do: First permissions review dated (Extranet permissions review).
- To do: Procedure for ended partnerships agreed with the relationship managers.
- To do: Unactivated registrations cleared regularly (Roles and policies, 7).
Related pages
- Extranets and partner portals
- Intranet rollout checklist
- Go-live checklist template
- Security review checklist for hosts
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.