I am changing plans. What happens to my projects?
Design a plan change or pause around timing, existing projects, limits, team work and a clear confirmation of future access.
Article language: English

In this article
“From 1 December: Small plan. Two active projects. Your seven existing projects will remain available to read.” This says more than a card with six green ticks. It still leaves questions: can the two selected projects be edited, who chooses them, and what happens to links sent to clients?
This is a proposed message for a fictional design studio's portal. The company is reducing its plan after a major assignment. It already has completed materials, invited clients and configured reminders. It is not choosing a service from scratch; it is deciding how to continue working with what exists.
The change screen should show the effects on that particular workspace. A plan name is shorthand. A person wants to know whether tomorrow they can open a project, edit a comment and receive a client's reply. A lower plan should not require a doctorate in comparing footnotes.
Compare the current state with the future state
A guide to B2B service pricing (in Polish) helps people understand an offer. For an existing client, a price list alone is not enough. Alongside the available capabilities, show which are in use and how the change affects them. “Fewer active projects” leaves a different question from “you have seven, and the plan allows you to edit two.”
Start with effects visible to the user: editing, reading existing material, creating new material and continued sharing. Do not combine them into one “restricted access” state. Someone may be able to view a project but not add comments, or keep an existing rule running without being able to change its settings.
Notion's downgrade guide says that, on the Free plan, existing automations continue to run but become view-only. They cannot be edited and new ones cannot be created. This is a product-specific example of separating execution from editing, not a rule every portal should copy.
Slack's free-plan limitations instead say that existing workflows stop working after a downgrade and new ones cannot be created. A similar plan-change label therefore conceals a different effect on automated work. The interface should show the decision made by its own system.
For our studio, show three areas already in use before presenting a large feature table: seven projects, links for four clients and two reminder rules. Give the current and future state for each. A full plan comparison can remain available nearby; the impact summary should not disappear among features the company has never used.
Do not call retained material “safe” when all that has been established is read access. Say what will remain available and how. Can files be downloaded? Is history available? Do old links lead to the same view? These statements can be compared with the product's behavior.
Seven projects and two editing slots
Assume this rule for our example: the client chooses two projects to continue editing and the rest remain read-only. It is a design assumption that the service owner would need to approve before implementation. It does not follow from the products above.
The selection should show project names and their current state. Establish what counts against the limit. A finished project, a draft and an archived folder may mean different things in a service. Here, a slot is occupied by a project chosen for editing, not every historical item. Show this next to the counter: “1 of 2 projects selected for editing.” Closing a finished assignment should not appear to mean deleting it to free a slot.
Someone may want to keep editing a small project that is still underway rather than the largest folder. Automatically retaining the two most recently opened items would make that decision for them, although opening a file alone is not sufficient grounds.
Explain each choice: “Remains editable” or “Read-only after the change.” A checkbox alone is not enough if it is unclear whether selected items are being kept or restricted. With seven projects the mistake may still be reversible through a conversation. With dozens, it stops being an amusing attention test.
If active projects can be exchanged later, explain that during selection. If they cannot, say so before confirmation. The rule matters to the decision to downgrade now; do not leave it to be discovered after the first click on “Edit.”
A collaborator limit requires a separate decision. Does someone lose access, or is only inviting additional people restricted? Choosing editable projects should not secretly choose people as well. Map the dependencies and show effects beside the resource or person concerned.
The instruction itself also has an actor. A project editor may not be authorized to change the whole company's plan. Their screen can show the current scope and a way to ask the workspace owner. Do not describe sending that request as a scheduled change. Confirmation should identify who still needs to decide. The owner, in turn, needs to see which workspace the button concerns, particularly when managing several clients.

A guide to sharing a link with defined access (in Polish) explains why recipients need to understand permissions. A plan change adds the question of whether those permissions remain. If a link will stop working, the project owner should see that before changing plans, and the client should later receive an understandable state instead of an unrelated page error.
For a project in progress at the transition, consider an open comment form. A worker may begin typing before the restriction takes effect. The save message must explain what was accepted and what can be done with unsent text. Do not hide lost editing access behind a generic server error.
The same applies to a client invited to approve work. If a plan prevents their response from a particular date, informing the administrator is not enough. The client needs an appropriate view too, naming the project and providing a way to contact someone. An external person should not be urged to buy a higher plan they cannot change. The workspace owner is responsible for access to their tool.
A pause has its own scope
A pause is sometimes treated as one large button that stops everything. A real product must define which actions stop and which remain available. The word alone does not say whether clients can see published material or whether reminders continue.
Shopify's description of the legacy Pause and Build plan distinguishes admin access and product editing from a disabled checkout for stores already on that plan. Its current description says the plan is unavailable to new stores and cannot be reselected after switching away. It illustrates the separation between editing and purchasing, not an option available to every store.
In our studio portal, a proposed pause might stop new projects and automatic reminders while keeping the archive readable. Write exactly that rather than “Your account will go to sleep.” The user should not have to guess whether the archive went to sleep too or who will wake it up.
Describe resumption against the same resources. In our example, decide whether overdue reminders will be sent, skipped or set up again. A sensible proposal for the studio is a list of overdue reminders to review before restarting. In this example they are not sent automatically. A client who approved a project another way long ago should not receive a ceremonial reminder a month later for work already closed. The rule must be visible when work resumes.
Closing an account and transferring shared projects (in Polish) involves a different decision. Do not use one “End” button for pausing, reducing a plan and deleting a workspace. The distinction should follow from action names and described effects, not the order of three confirmation dialogs.
If the company itself is ending a service, existing customers need a service retirement process (in Polish). Do not present a forced ending as a voluntary choice of a smaller plan. The portal owner and the client make different decisions, although both scenarios may reduce what is visible on screen.
Show two dates when they describe two states
The date an instruction is accepted need not be the date access changes. In our example, the owner selects a plan today and the new scope takes effect on 1 December. Until then the panel should show the current plan and the scheduled change. Repainting the entire account as “Small” immediately after the click would conceal the actual state.
Give the effective time according to the service's rule. Where the hour and time zone matter, include them in the confirmation. Do not infer a date from a cycle label when the system stores a different time. The design should use the same confirmed information on which the access change actually depends.
A guide to product change logs (in Polish) distinguishes an announcement from a feature becoming available. Apply the same clarity to a client's decision. “Change scheduled” confirms a different outcome from “New plan active.” Our confirmation should also list the two selected projects and a route back to that setting. A date alone will not reveal that the wrong project was left editable. The user should be able to compare the saved selection with what they just chose.
If the user returns before the date, continue to show the pending instruction. If it can be cancelled, show the action and its effect. If another change is selected, explain whether it replaces the earlier one. A list of several apparently active commands is not a history on which to base a decision.
When confirmation is missing, do not immediately encourage “Try changing again.” The instruction may have been accepted despite a lost response. The panel should first let the user establish its current state and then choose the next step. On returning to settings, they should see a recognizable state: scheduled change, no change, or an outcome not yet confirmed. Each message calls for a different action.
Aeneia Design can discuss the presentation of such a panel, including states, resource selection and confirmation copy. Work on screens first requires the service's actual rules. A mockup does not establish data retention rules or the effective time of an access change.
After implementation, begin a trial with a workspace already in use, with materials and shares. An empty account will not reveal which of the seven projects disappeared from the list or why a client lost the ability to reply. Go through the change before and after it takes effect, including from an old link.
The participant should be able to explain in their own words when access will change, what they can still open and what they must select beforehand. Only then should they confirm the instruction. Understanding the effects is a better acceptance condition than merely noticing the new plan name.







