AIUNIFY PROS SUITE does not use one universal Save, History, Projects, or Files system across every Tool.
Instead, persistence is implemented on a Tool-by-Tool basis.
Some specialized PROS SUITE Tools provide persistent:
Many other Tools—especially Tools using Standard ToolPage—provide only:
and do not provide persistent Save or History.
Throughout PROS SUITE, several different operations can appear similar but have very different results.
These include:
Understanding the difference is important.
A true saved project is stored by the Tool so that it can later be reopened and continued.
Source-verified examples include:
Some generation Tools automatically display previously generated assets.
Examples include:
Several AI Marketing design Tools maintain their own asset collections.
Examples include:
Certain Marketing assets can be reused inside other Marketing Tools.
Source-verified examples include:
A Download creates or opens a file for use outside PROS SUITE.
A downloaded file should not automatically be assumed to appear inside:
Website Builder supports both:
Saving keeps the Website project available for continued work.
Publishing makes the Website available through its publishing workflow.
Many generated results exist only inside the current page state until they are:
The current subscriber source does not establish one global My Projects workspace containing every type of AIUNIFY PROS SUITE creation.
Saved Website projects remain within Website Builder.
Saved Presentations remain within Pitch Deck.
Saved Games remain within Game Developer.
Marketing assets remain inside their Marketing-specific histories and collections.
The current source does not establish a central:
My Files
workspace containing every file uploaded or generated across PROS SUITE.
There is no source-verified History page that combines every generation from every Tool.
The inspected subscriber source does not establish global:
for all PROS SUITE content.
There is no source-verified global search interface specifically for searching all:
from one saved-content repository.
The current source does not establish a universal Recycle Bin for deleted Projects or Assets.
Where a Tool provides irreversible Delete confirmation, treat deletion accordingly.
A large number of PROS SUITE Tools use the shared Standard ToolPage.
Its current source stores local:
state and provides Generate, Reset, Copy, and Download.
Copy places the current Output on the browser Clipboard.
Current confirmation:
Copied!
Content copied to clipboard.
Download creates a plain-text file using:
[tool-id]-output.txt.
Reset clears:
and refocuses the Prompt Textarea.
The shared ToolPage does not contain a universal:
Save
operation.
It does not contain a universal:
Generation History
list.
Generating content in a Standard ToolPage does not automatically create a reusable PROS SUITE project.
For important Standard ToolPage output:
Most Standard writing generators do not maintain saved generation History.
Standard Social content generators do not automatically create persistent Social-content projects.
Standard Marketing and Sales ToolPage output should be preserved using Copy or Download when needed.
Standard Business Tools likewise do not gain persistent project storage simply because they produce structured business content.
Standard Lesson Plan, Study Guide, Flashcard, Rubric, Vocabulary, Debate, and similar ToolPage content should be preserved externally unless the individual Tool explicitly implements persistence.
Standard Story Ideas, Character Creator, Song Lyrics, Joke, and Name Generator output is not automatically added to a universal Creative archive.
Generated Privacy Policies, Terms, Disclaimers, and Refund Policies should be copied or downloaded before leaving the Tool.
Meta Description, Keyword Research, SEO Audit Checklist, and Schema Markup Standard ToolPage results are not persistent SEO projects.
Journal Prompts, Goal Setting, and Motivation use Standard ToolPage and do not provide universal persistent histories.
Standard Data Visualizer, CSV Analyzer, Survey Builder, and KPI Dashboard results do not become stored analytical projects.
Symptom Journal, Meal Plan, and Workout Builder currently use Standard ToolPage, so their generated output should be copied or downloaded if it needs to be retained.
Website Builder is one of the clearest examples of a PROS SUITE Tool with genuine saved projects.
When a Website is saved, the workspace sends the current:
into the Website saving workflow.
Successful Website saving displays:
Website Saved Successfully!
When a newly saved Website receives a Project ID, Website Builder adds:
projectId
to the current browser URL.
If the URL already contains a Project ID, that ID is included in the next Save request.
This allows an existing Website project to be updated rather than automatically creating a separate new project every time.
The current Save workflow uses:
userpromptas the project name.
The current Website saved-project UI does not expose a separate Rename control.
Website Builder can load a saved project by its Project ID.
Loading restores the saved Website code.
The saved Website's working Messages are also restored.
If the saved project contains a Subdomain, the workspace restores that project Subdomain state as well.
If loading fails, Website Builder can display:
Failed to load project.
Website Builder fetches the subscriber's Website projects and displays them as project Cards.
Each saved Website Card contains a scaled Website Preview rendered in an iframe.
Each Card displays its saved Website name.
Each Card also displays:
Last updated: [date].
Select:
Edit
to reopen the saved Website project in the Website workspace.
Each saved Website Card also provides Delete.
The confirmation dialog is:
Delete Project
with:
Are you sure you want to delete this project? This action cannot be undone.
Successful deletion displays:
Project deleted.
If no Website projects exist:
No projects yet. Create your first AI website!
The current Website saved-project section does not provide Search.
There is no source-verified Filter control.
There is no subscriber Sort interface.
Website projects are not shown in user-created Folder structures.
There is no Tag-management interface.
The current saved Website Cards do not show a Duplicate action.
There is no separate Rename button in the verified Project list.
Save preserves Website project state for future editing.
Publish uses the Website save workflow while also assigning the chosen Subdomain.
Current success message:
Website Published to Subdomain!
If the Website did not yet have a Project ID, publishing can return one and update the URL.
The source also supports clearing the Website's Subdomain through Unpublish.
Successful action:
Website unpublished!
The saved Website project remains conceptually different from its published state.
Pitch Deck supports persistent saved Presentation projects.
The Presentation workspace saves:
The saved Presentation name is derived from the:
first slide title.
If none exists, the fallback is:
Untitled Presentation.
The current save logic removes HTML tags from the first-slide Title before using it as the saved Presentation name.
Successful Save displays:
Presentation saved successfully!
A newly saved Presentation can add its generated Project ID to the current URL.
When projectId is present, the Presentation workspace loads that saved project.
The saved Slide collection is restored.
The saved Presentation Message history is also restored.
Current error:
Failed to load presentation project
or:
Error loading presentation project.
The Pitch Deck landing workspace contains:
Your Saved Presentations.
Current description:
Click to edit or present your saved decks.
Each saved deck Card can show a miniature first-slide Preview.
The Preview displays the number of Slides.
The Card displays the saved Presentation name.
Each Card shows:
Updated [date].
Select:
Edit
to reopen the saved Presentation in Pitch Deck.
Select:
Play
to open the saved deck in Presentation Play mode.
Each saved Presentation Card includes a Delete action.
Current confirmation:
Delete Presentation
with:
Are you sure you want to delete this presentation? This action cannot be undone.
Successful deletion displays:
Presentation deleted successfully.
If no presentations have been saved:
No saved presentations yet.
with:
Generate one using the prompt box above and save it to see it listed here!
The current saved Presentation UI does not provide Rename.
Changing the first-slide Title can influence the name used on a later Save.
There is no source-verified Duplicate Presentation action.
Saved Presentations are displayed as a collection rather than organized into subscriber-created Folders.
No Tag interface is source-verified.
The current Saved Presentations section does not provide dedicated Search.
No user-facing Sort control is established.
Game Developer contains its own:
Saved Games
collection.
When generated HTML exists, the workspace displays:
Save Game.
Current Save Game submits:
The Game name is automatically constructed from the first 30 characters of the Prompt.
If the Prompt is longer than 30 characters, an ellipsis is added.
Current success:
Game saved successfully!
After Save, the current Saved Games collection is fetched again.
Although Difficulty can affect game generation, the current Saved Game record does not include it in the source-verified Save operation.
The current Save payload does not include the Mobile-Friendly configuration.
A generation reference Image is not stored by the current Save Game payload.
Those additional generation configuration values are also not part of the current Save Game request.
The Saved Game structure source-verifies:
as the core reusable state.
The page contains:
Saved Games.
Each Saved Game Card includes a scaled iframe Preview of the saved HTML.
Each Card displays the generated saved Game name.
The Card displays the saved Genre.
Each saved Game shows its updated Date.
The saved Prompt is displayed beneath the Game information.
Select:
Play Again
to load the saved Game's:
back into the active Game workspace.
The current Play Again workflow scrolls to the workspace and then attempts to enter Fullscreen.
Each saved Game provides Delete.
Current dialog:
Delete Game
with:
Are you sure you want to delete this game? This action cannot be undone.
Current empty state:
No saved games yet
with:
Build your first game and save it to see it appear here in your collection.
Save Game preserves a Game within the PROS SUITE Saved Games collection.
The separate Download action creates:
game-[timestamp].html.
Current Download message:
Downloaded!
with:
Game saved as HTML file.
A browser-downloaded .html file is external.
A Saved Game appears inside the Game Developer Saved Games collection.
AI Marketing generation Tools maintain asset-specific histories and collections rather than using the Website/Pitch Deck project model.
Source-verified persisted Marketing asset types include:
Route:
/ai-marketing
The AI Marketing Studio Dashboard contains:
Recent Assets.
The Dashboard fetches Marketing assets and keeps only:
imagevideotypes for this section.
The current Dashboard takes:
the first eight
matching Image/Video assets.
Because it is limited to:
the AI Marketing Studio Recent Assets section should not be treated as a complete archive of every Marketing asset.
For example, the Dashboard filtering does not place:
into that Recent Assets grid.
Those assets are managed through their respective Tool pages.
Current empty state:
No assets yet
with:
Start generating your first marketing assets to see them here.
The empty-state action routes the subscriber to Image Generator.
The Dashboard displays:
View All Gallery.
In the inspected source, this Button does not contain a source-verified Link or click action.
Therefore:
Do not rely on View All Gallery as a functional all-assets navigation control in the current version.
Image, Video, and other supported Marketing collections can use the shared:
MarketingAssetCard.
The Card can contain:
The Card includes a View action for visual assets.
For Music assets, the primary Card action uses a Play icon rather than Eye/View.
Asset Cards support Download.
A Share-style action copies the underlying asset URL.
Current confirmation:
Link copied to clipboard.
This action copies the hosted URL string.
It does not place the actual Image/Video binary on the Clipboard.
Shared MarketingAssetCard uses:
marketing-[type]-[first 8 characters of id].[extension].
Standard visual Image assets use:
.png
in the shared Card Download function.
Video assets use:
.mp4.
Music assets use:
.mp3.
Successful asset download displays:
Download started.
The shared MarketingAssetCard shows Delete only when the parent Tool provides an:
onDelete
operation.
The existence of a Trash icon inside the shared Card component does not mean every page supplies a Delete function.
The current AI Marketing Studio Recent Assets mapping supplies an onClick viewer action but no source-verified onDelete callback.
The current Image Generator History cards are passed into MarketingAssetCard for viewing without a source-verified Delete handler.
The same applies to the verified Video Gallery mapping.
Selecting a supported visual Asset opens:
AssetViewer.
Images are loaded as Lightbox Slides.
The Asset Viewer includes the Zoom plugin.
Video assets are passed to the Lightbox Video plugin.
Video viewing enables:
AssetViewer can move among the Asset list supplied by the current Tool.
AssetViewer does not source-verify controls for:
Route:
/ai-marketing/image-generator
When authenticated, Image Generator fetches previously generated Image assets.
After a successful Image generation, the page:
The Image Generator section is:
Generation History.
Each stored Image is shown through MarketingAssetCard.
Selecting a History Card opens AssetViewer.
Current empty message:
No history found.
Image Generation History does not expose dedicated Search.
There is no user-facing Filter selector.
The inspected page does not establish a pagination interface.
There is no source-verified Rename action.
Route:
/ai-marketing/video-generator
The page fetches saved Video assets from the Marketing asset list.
Successful Video generation refreshes the Video asset list.
The History section is titled:
Video Gallery.
Each Video is shown using MarketingAssetCard.
Selecting a Video opens AssetViewer with Video playback controls.
Current message:
No video history found.
No Rename control is source-verified.
The current Video Gallery does not provide subscriber-created Folders.
Music Generator contains:
Generation History
with the description:
All your previous musical creations in one place.
The Music workspace calls its History-loading function when the page initializes.
After a successful generation, the workspace:
The Music History Header provides:
Refresh History.
During refresh:
Refreshing....
History Cards provide Play/Pause playback.
The Card can display the Model used.
Fallback:
Suno V5.
The Card displays:
Stored Style is displayed when available.
Fallback:
Original Audio.
The Music Card displays the creation Date when available.
Each History Card displays:
Save.
The current Save action on a Music History Card calls:
window.open(asset.url, '_blank').
Therefore:
This Save control opens the Music asset URL in a new browser tab. It is not the operation that initially persists the track into Music Generation History.
The track is already present in Generation History before that History-card Save link is selected.
Music History also provides:
Isolate
to begin the Audio Isolation workflow.
Current isolation message can state:
Task Created
and:
Isolation task started: [task]. You will see it in history soon.
If no creations exist:
No creations yet
with:
Start by generating your first track in Normal or Custom mode.
The current Music History cards do not establish a user-facing Delete control.
There is no Rename action in the inspected Music History UI.
No subscriber-created Music Folder system is source-verified.
Logo Generator loads previously generated Logo assets.
The saved Logo section is:
Your Work
Current description:
Your personal collection of AI-crafted brand identities.
The section shows the total:
Design
or:
Designs
count.
Logo Cards display the saved Logo Image.
A saved Logo can be opened in the Asset Viewer.
Saved Logo Download uses:
logo-[id].png.
The third saved Logo action restores the Logo to the active Result area and restores its Brand Name from Metadata where available.
A saved Logo created within the current code's 24-hour condition receives:
Latest.
Current empty state:
No masterpieces yet
with:
Your future brand icons will be archived here in high resolution.
The inspected saved Logo Card does not expose a Delete action.
The Manga workspace loads previously generated assets of Type:
manga.
The saved Manga section is:
Your Archive.
Current wording:
Your collection of AI-crafted manga illustrations.
The Archive shows the number of:
Illustration
or:
Illustrations.
Selecting a Manga Image can open the Asset Viewer.
A Manga archive entry is an asset record, not a multi-page manuscript/project-management system.
The YouTube Thumbnail page fetches:
thumbnail
Marketing assets when authenticated.
The page displays:
Your Thumbnails.
Current description:
Archive of your AI-generated YouTube thumbnails.
The page displays the number of stored Thumbnails.
A saved Thumbnail can be opened in Asset Viewer.
Current filename:
thumbnail-[id].png.
The third Card action loads the saved Thumbnail back into the current Result area and restores its saved Video Title Metadata where available.
Recently created Thumbnails can receive:
Latest.
Current empty state:
No thumbnails yet
with:
Your future viral thumbnails will be archived here.
Flyer Designer fetches saved Marketing assets of Type:
flyer.
The saved Flyer section is:
Design History.
Current wording:
Access your previously generated flyer layouts.
Saved Flyer cards can be opened in the Asset Viewer.
Current filename:
flyer-[id].png.
The third action loads the selected saved Flyer into the active Result and restores its Title Metadata where available.
Current empty state:
No flyer layouts in your catalog
with:
Generate your first business flyer to see it listed here.
The page fetches saved Marketing assets of Type:
business-card.
The saved section is:
Design History.
Current wording:
Access your previously generated business card layouts.
Saved Cards can be opened in AssetViewer.
Current filename:
card-[id].png.
The third action restores the selected Business Card to the active Result and restores its stored Name Metadata where available.
Current empty state:
No business card mockups in your catalog
with:
Generate your first premium business card mockup to see it listed here.
The page fetches saved Marketing assets of Type:
brochure.
The saved section is:
Design History.
Current wording:
Access your previously generated brochure spreads.
Saved Brochures can be opened in AssetViewer.
Current filename:
brochure-[id].png.
The third action restores the saved Brochure into the current Result area and restores its Title Metadata where available.
Current empty state:
No brochure layout spreads in your catalog
with:
Generate your first double-sided or tri-fold brochure spread to see it listed here.
The saved Flyer collection is primarily an asset archive.
It does not source-verify a fully editable vector business-card document.
It does not create a multi-page desktop-publishing project with individual editable text boxes.
The Refresh/Reuse action brings the saved visual back into the current Result area.
It should not be described as restoring every original generation parameter unless the source explicitly does so.
Avatar Studio fetches the subscriber's available Avatars through its Marketing Avatar list.
Current message:
No avatars created yet. Use the tool on the left to start.
When Avatars exist, the page displays them as reusable Avatar items.
Selecting an Avatar can open the associated visual asset in the Viewer.
Marketing Tools that support Avatar references can display:
Select AI Avatar.
The Picker obtains the saved Avatar list.
Selecting an Avatar passes that saved Avatar into the current Marketing workflow.
The Picker also provides:
New Avatar
which links back to Avatar Studio.
This makes Avatars one of the clearest examples of a persistent Marketing asset intended for reuse across supported tools.
The Avatar Studio source provides a Delete operation for deletable user Avatars.
Current success:
Avatar deleted.
Current dialog:
Delete Avatar
with:
Are you sure you want to delete this avatar? This action cannot be undone.
The current Avatar display differentiates system Avatars, and the delete UI is not applied the same way to system entries.
Subscribers should not expect every Avatar to be deletable.
Some Marketing Tools provide:
Select Product Reference.
ProductPicker fetches previously uploaded Product references so they can be reused.
The Picker provides:
Upload Product.
The file chooser accepts:
image/*.
The upload handler checks that the selected file's MIME Type begins with:
image/.
Current error:
Please upload an image file.
When uploaded, the Product Reference name is derived from the original filename without its extension.
Current message:
Product uploaded successfully.
After successful upload, the Product list is refreshed.
Current state:
No products uploaded yet.
Saved Product Images can later be selected by supported Marketing Tools.
Uploading a Product Image does not create a general-purpose PROS SUITE File entry that can be managed everywhere.
It creates a reusable Marketing Product Reference.
The ProductPicker does not expose Rename.
The inspected ProductPicker does not provide a Delete action.
The Reel Generator includes a function that loads previous Reels through:
list-reels.
Reels should therefore be treated as part of the Reel Generator's specialized persistence rather than as a universal PROS SUITE project type.
The inspected source confirms a Recent Reel list is loaded but does not establish a global Media library containing all Reel projects.
Some PROS SUITE Tools accept an Image or Document only as temporary Input for the current operation.
Uploading a reference Image to a generator does not automatically prove that the Image becomes part of a persistent reusable library.
ProductPicker is a clear exception because it explicitly saves the uploaded Image as a reusable Product Reference.
Created Avatars are loaded later and can be selected from AvatarPicker.
Some specialized Tools, such as the Live Chat Knowledge Base workflow documented earlier, manage their own uploaded Knowledge Base content.
That does not establish a global My Files system.
When the browser downloads a file, that file becomes external to the PROS SUITE project/history system unless the Tool separately stores it.
Standard ToolPage creates:
.txt
files.
Game Developer can create:
.html
files.
Marketing generation Tools can download formats such as:
depending on asset type.
Pitch Deck's PowerPoint export creates a local .pptx file as documented in Chapter 17.
That exported PowerPoint should not be confused with the persistent saved Presentation Project inside PROS SUITE.
Website Builder's downloadable Website source and its persistent Website project are likewise separate concepts.
| ActionResult | |
| Save Website | Persistent PROS SUITE Website project |
| Download Website | External browser file |
| Save Presentation | Persistent PROS SUITE Presentation |
| Export PowerPoint | External .pptx |
| Save Game | Persistent Saved Game |
| Download Game | External .html |
| Standard ToolPage Download | External .txt |
| Marketing Asset Download | External media file |
Website Builder, Pitch Deck, and Game Developer require a direct Save workflow for their project-style persistence.
Image, Video, Music, and specialized Marketing generation workflows can place successfully generated assets into their Tool-specific histories.
An Image in Generation History is not necessarily an editable layered Image project.
A Pitch Deck can be saved as a project without having been exported to PowerPoint.
Website Builder is the clearest Tool where Save and Publish coexist.
A Website can remain a saved working project without being publicly published.
Publishing uses the Save workflow and associates publishing information with the project.
Removing the published Subdomain does not equal deleting the underlying Website project.
Website projects support explicit Delete with irreversible confirmation.
Saved Presentations support explicit Delete with irreversible confirmation.
Saved Games support explicit Delete with irreversible confirmation.
Deletable non-system Avatars support explicit Delete with irreversible confirmation.
Do not assume all Marketing asset histories support Delete.
The shared Card only renders Delete when the parent workspace supplies a Delete handler.
The verified irreversible Delete dialogs do not establish a universal Undo/Restore system.
Current Website Save naming is based on the Website's Prompt or fallback name.
Presentation name is derived from the first Slide Title.
Game name is derived from the first 30 characters of the Prompt.
Different Marketing generators use different Prompt/Metadata naming conventions.
A global asset/project Rename function is not source-verified.
Not source-verified.
Not source-verified.
Not source-verified.
Not source-verified.
Not source-verified.
Not source-verified.
Not source-verified.
Tool-specific histories already restrict themselves by Asset Type, but there is no broad user-configurable global filter system.
No source-verified global Folder management exists for saved PROS SUITE content.
No global Asset Tagging interface is established.
No global Bulk Delete workflow is source-verified.
No universal Bulk Download is established.
No global Move operation exists because a universal Folder system is not source-verified.
| Tool / AreaPersistence Verified?Type | ||
| Standard ToolPage | No universal persistence | Temporary Output |
| Website Builder | Yes | Saved Projects |
| Pitch Deck | Yes | Saved Presentations |
| Game Developer | Yes | Saved Games |
| Image Generator | Yes | Generation History |
| Video Generator | Yes | Video Gallery |
| Music Generator | Yes | Generation History |
| Logo Generator | Yes | Your Work |
| Manga Generator | Yes | Your Archive |
| YouTube Thumbnail | Yes | Thumbnail Archive |
| Flyer Designer | Yes | Design History |
| Business Card Designer | Yes | Design History |
| Brochure Designer | Yes | Design History |
| Avatar Studio | Yes | Avatar Collection |
| ProductPicker | Yes | Product Reference Assets |
| Reel Generator | Yes, recent list verified | Tool-specific Reels |
| CapabilityWebsitePitch DeckGame Developer | |||
| Explicit Save | Yes | Yes | Yes |
| Reopen | Yes | Yes | Yes |
| Preview | Yes | Yes | Yes |
| Edit/Reopen | Yes | Yes | Play Again/reload |
| Delete | Yes | Yes | Yes |
| Rename | No dedicated control verified | No dedicated control verified | No |
| Duplicate | No | No | No |
| Search | No | No | No |
| Folders | No | No | No |
| Tags | No | No | No |
| AssetViewDownloadReuseDelete Verified | ||||
| Image History | Yes | Yes | Not as project | No |
| Video Gallery | Yes | Yes | Not as project | No |
| Music History | Play | Opens asset URL | Isolate | No |
| Logo | Yes | Yes | Yes | No |
| Manga | Yes | Tool-specific | Tool-specific | No |
| Thumbnail | Yes | Yes | Yes | No |
| Flyer | Yes | Yes | Yes | No |
| Business Card | Yes | Yes | Yes | No |
| Brochure | Yes | Yes | Yes | No |
| Avatar | Yes | Reusable | Yes | Non-system avatars |
| Product Reference | Yes in Picker | Used as reference | Yes | No |
When using:
use the Tool's explicit Save workflow before leaving when you need the work retained.
If a Tool uses Standard ToolPage and the result matters:
Download it before leaving.
Copying content into an external document can provide another preservation option.
When a specialized Tool provides an Export or Download format, preserve the finished deliverable separately from the editable PROS SUITE project/history.
Browser navigation is not a Save system.
Temporary page state should not be treated as persistent storage.
Generate the Website.
Refine design and content.
Use the Website Save operation.
Wait for:
Website Saved Successfully!
Return to the Projects list and confirm the Project Card exists.
Use:
Edit
from the saved Project Card.
When ready, use the publishing workflow.
Download source if an independent backup is appropriate.
Create the Presentation.
Use Design Chat and available deck editing controls.
Select the Presentation Save action.
Wait for:
Presentation saved successfully!
Confirm it appears under:
Your Saved Presentations.
Use:
Edit.
Use:
Play.
Use PowerPoint Export when an external .pptx is needed.
Build the Game.
Use the live Game Preview.
Select:
Save Game.
Wait for:
Game saved successfully!
Confirm the Game appears in:
Saved Games.
Use:
Play Again.
Download the HTML when an external standalone file is needed.
Create the Marketing asset.
Wait for the Tool's success state.
Confirm the generated Asset appears in that Tool's:
where supported.
Use the Asset Viewer.
Download the approved final media when needed.
For Tools supporting reuse, load the prior asset back into the active creation workspace.
Do not treat a Tool-specific gallery as the only backup of business-critical media.
If the Tool uses Standard ToolPage, there may be no persistent History.
Use:
before leaving.
This is expected.
Download and Save Project are separate operations.
Reset intentionally clears current local Input and Output.
Standard ToolPage does not maintain universal generation History.
If it was not copied/downloaded, it may not be recoverable through the Tool UI.
Confirm that:
Website Saved Successfully!
was displayed before leaving.
If the current URL contains a Project ID, Save updates that project.
The current Save uses the Website's Prompt as its project name, with New Website as fallback.
A dedicated Rename action is not source-verified in the current saved-project UI.
No Duplicate action is currently source-verified.
The saved name is derived from the first Slide Title.
That is the fallback when no usable first-slide Title is available during Save.
No dedicated Rename control is source-verified.
Use:
Play
from Your Saved Presentations.
Use the separate PowerPoint Export workflow.
Saving the deck alone does not create the external .pptx.
The current name uses only the first 30 Prompt characters plus an ellipsis when needed.
Current Save preserves:
but does not include all generation settings.
Download HTML and Save Game are separate actions.
No source-verified Rename control exists.
The Dashboard's Recent Assets implementation limits itself to the first eight Image/Video assets.
The Dashboard filters Recent Assets to:
Other Marketing asset types remain in their specialized Tool collections.
The current inspected Button has no source-verified action attached.
Use the individual Marketing generator History/Gallery sections instead.
Refresh or reopen Image Generator.
The page fetches its Image asset list when authenticated.
Reopen or refresh the Video Generator and confirm the generation completed successfully.
Current Image and Video gallery mappings do not source-verify a Delete handler.
Copy Link copies the hosted URL.
Use Download for the actual media file.
Select:
Refresh History.
That is consistent with the current Music History implementation.
The History-card Save action opens the stored asset URL.
A user-facing Delete action is not source-verified in the current Music History.
The isolation workflow indicates that the Task will appear in History after processing.
Use Refresh History as appropriate.
Open Flyer Designer and review:
Design History.
Open Business Card Designer and review its:
Design History.
Open Brochure Designer and review its:
Design History.
Open Logo Generator and review:
Your Work.
Open YouTube Thumbnail Generator and review:
Your Thumbnails.
Open Manga Generator and review:
Your Archive.
Confirm that the selected file is recognized by the browser as an Image.
The current Upload Product workflow derives the Product name from the filename.
A Rename control is not source-verified in ProductPicker.
After a successful upload, ProductPicker refreshes its Product list.
If necessary, reopen the Picker.
Before relying on future access, determine whether the Tool is:
For Website Builder, Pitch Deck, and Game Developer, Save once the project reaches a useful state.
Do not assume every edit is auto-saved unless the Tool explicitly says so.
Persistent project storage and external deliverables serve different purposes.
Use both when appropriate.
Important:
should not rely on one application History as their only business archive.
Some Tool names are derived directly from:
so meaningful starting text improves later identification.
Several Delete dialogs explicitly state that deletion cannot be undone.
A collection of generated assets is not the same as version-management software.
When an asset is final, preserve the approved external version.
PROS SUITE uses terms such as:
These are separate Tool-specific systems.
The existence of a History section does not mean every intermediate edit is stored as a recoverable version.
There is no global:
Restore Previous Version
system across PROS SUITE.
Examples include:
Marketing assets can have hosted URLs that the UI can copy to the Clipboard.
A hosted Asset URL points to a resource.
A Download creates an external local file.
Some Marketing assets contain Metadata such as:
depending on asset type.
The source does not establish a subscriber File Explorer with directories and file-management controls.
A file supplied to a specific Tool should be treated as Tool-specific Input unless persistence is explicitly shown.
ProductPicker explicitly saves uploaded Product Images for reuse.
Supported specialized Marketing generation results can be loaded later through their respective Histories.
Not source-verified.
Not source-verified.
Not source-verified.
The current source does not establish a subscriber-facing universal File-storage quota interface.
Not source-verified.
Not source-verified.
There is no source-verified Google Drive-style file-permission manager across PROS SUITE.
Some specialized PROS SUITE Tools maintain other subscriber-specific state.
Trading Terminal can maintain items such as:
as documented in Chapter 31.
These are persistent Tool records—not Files or Saved Projects.
Other specialized Tools can maintain configuration or connection state.
Those should remain documented inside their respective chapters rather than being treated as File assets.
For Website, Presentation, or Game projects, use the Tool's saved collection to reopen them.
For supported Marketing Assets, use the generating Tool's History or Archive.
For Standard ToolPage content that was not downloaded or copied, no universal recovery method is source-verified.
Where the Delete dialog states the action cannot be undone, the subscriber should not expect a Tool-level recovery option.
Use:
Save
for continued editing.
Use:
Publish
for public availability.
Use:
Download
for an external copy where provided.
Use:
Save Presentation
for continued editing.
Use:
Play
for presenting.
Use:
Export PowerPoint
for a .pptx.
Use:
Save Game
for Saved Games.
Use:
Download HTML
for a standalone file.
Check the Tool's:
after successful generation.
Use:
Copy or Download
before leaving if the result needs to be retained.
Website Builder currently supports:
It does not establish subscriber-facing:
Pitch Deck currently supports:
It does not establish:
Game Developer currently supports:
It does not establish:
AI Marketing Studio currently supports:
It does not establish:
Image Generator currently supports:
It does not establish:
Video Generator currently supports:
It does not establish:
Music Generator currently supports:
It does not establish:
Logo Generator source-verifies:
Manga Generator source-verifies:
YouTube Thumbnail Generator source-verifies:
Flyer Designer source-verifies:
Business Card Designer source-verifies:
Brochure Designer source-verifies:
The current Marketing system source-verifies:
ProductPicker source-verifies:
Ask:
The central finding of Chapter 47 is that AIUNIFY PROS SUITE does not implement one universal Save/History/File repository for every Tool.
Instead, persistence is tied to individual specialized workflows.
Website Builder provides genuine saved Website projects.
Its Save workflow stores the current Website Code and Messages, updates an existing Project when a Project ID exists, and creates a Project ID for new saves.
Saved Website Cards provide:
and deletion is presented as irreversible.
Pitch Deck provides:
Your Saved Presentations
with Slide previews, Slide count, saved Name, Updated Date, Edit, Play, and Delete.
Presentation Save stores the current Slides and Design Messages. Its saved Name is derived from the first Slide Title, with Untitled Presentation as fallback.
Game Developer provides:
Saved Games
with Preview, Game Name, Genre, Updated Date, Prompt, Play Again, and Delete.
The current Save Game workflow preserves Code, Prompt, Genre, and Visual Style, while other generation settings such as Difficulty and Mobile-Friendly are not included in that Save payload.
AI Marketing Studio provides:
Recent Assets
but the Dashboard specifically filters to Image/Video assets and shows only the first eight.
Therefore, it is a recent visual-asset overview—not a complete universal Marketing Asset library.
Image Generator provides:
Generation History
and Video Generator provides:
Video Gallery.
Music Generator provides:
Generation History — All your previous musical creations in one place
with Refresh History, playback, track information, an asset-URL Save/Open action, and Audio Isolation.
The History-card Save action opens the asset URL; it is not the operation that originally persists the track.
Additional specialized Marketing Tools have their own persistent collections:
Avatar Studio and ProductPicker provide reusable Marketing references.
The current subscriber source does not establish a single My Files environment with:
Files and Assets remain associated with the Tools that create or use them.
The central operating principle for Chapter 47 is:
In AIUNIFY PROS SUITE, Save, History, Gallery, Archive, Download, and Publish are distinct operations. Website Builder, Pitch Deck, Game Developer, and specialized Marketing Tools provide source-verified persistence in different ways, while Standard ToolPage generators do not provide universal Save or History. Subscribers should use each Tool's specific persistence workflow and download or externally preserve business-critical final work when appropriate.