Guide: set up the system and the project
Do this once per installation and once per project, before phase 1. It makes the app safe to use and the project ready for people.
This page applies to the System and project configuration stage.
Project manager guide
Reach a project that the right people can open, with the right rules and with no surprises in sign-in, mail or AI.
- Install and sign in.
- Do now: Open the setup page after installation. Let it check the system, connect your company login and name the first administrator.
- Why: Until one administrator exists, nobody can change a setting or create a project.
- The app checks: Setup tests each part of the system by itself. It closes when it is finished and cannot be run again.
- Next: Sign in with your company account, then open Administration.
- Review the system settings.
- Do now: Open each settings group in Administration, such as Entra ID, Session, File storage and Notifications. Test the connection, then save.
- Why: The settings decide who may sign in, where files go and how long a session lasts.
- The app checks: A saved secret is never shown again. A banner lists settings that wait for an API restart, and each setting keeps its history.
- Next: Look at AI and extensions, or skip them if the customer does not want them.
- Decide on AI and extensions.
- Do now: Register an external model provider only when the customer allows it. Add an extension only for a service that must hear about project events.
- Why: Without a provider all AI runs locally. Anything sent to a provider cannot be called back.
- The app checks: A provider works only in a project with an approved AI policy. An extension host must be on the allowed list in the notification settings.
- Next: Create the project.
- Create the project.
- Do now: Choose New project. Enter a code, a name and the customer. Pick the mode, the default language, the IFS deployment option and whether there are several sites.
- Why: The mode decides which phases and pages you get. The project uses the default methodology pack.
- The app checks: Only a platform administrator can create a project. The code is 2 to 20 characters. A new implementation gets its gates at once.
- Next: Add the first members.
- Add members and roles.
- Do now: Open Members. Add each person with the smallest role that does the job. Start with both project managers, the sponsor and the system owner.
- Why: Roles decide what a person sees and who may approve. The steering group is built from confirmed role assignments.
- The app checks: Managing members needs the project administrator permission. Removing a role also takes that person out of open approvals for the role.
- Next: Check who approves what.
- Check the approval rules and privacy.
- Do now: Open Approval rules and read the steps for each object type. Open Privacy and learn how an erasure request runs.
- Why: You learn now, not at the gate, that a decision needs a person who is not in the project yet.
- The app checks: Nobody approves their own request. Some rules can be tuned for the project, and others are fixed by the pack.
- Next: Set notifications, the AI policy and your profile.
- Set notifications, AI policy and profile.
- Do now: Choose the channels of the project. Send the AI policy for approval if an external provider is used. Connect your calendar to find meeting times.
- Why: People then hear about approvals in time. The AI policy limits which data may leave the installation.
- The app checks: Required notification topics stay on. A policy needs approval by a person with the right role. The calendar link is optional.
- Next: Start phase 1 with the guide for the Initiate project stage.
Related topics
- First-time setup
- Administration
- New project
- Project members
- Approval rules
- Guide: phase 1, Initiate project
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: