Originally Posted by
dkoch
Not sure about this one. When you initially create a tool palette, ACA will make it in the top location on the Tool Palettes File Locations list (Options > Files). When you drag and drop that into a Tool Catalog in Content Browser, a copy of the palette and its tools gets made in the Palettes subfolder below the catalog's folder (and an Images folder below that for the tool images) and the catalog gets a reference to the palette ATC file.
When a palette is i-Dropped into a Workspace from a catalog in the Content Browser, a copy of that palette and its tools is added to the local Workspace (and saved to the top location in the Tool Palettes File Locations list). If you set the palette to be refreshable when you do the i-Drop, then the local copy will not be editable but will retain a link back to the catalog version. Even so, deleting the local i-Dropped version should not affect the catalog.
ACA can usually handle two or more palettes with the same displayed name, as it adds a GUID to the name and tracks that. I am not sure why deleting a local copy (either the original palette or the i-Dropped one) would affect the catalog copy, unless you had directly linked to the network location in your Tool Palettes File Locations and the version you deleted was the directly linked version. If you go with having office-standard palettes accessed directly through the Tool Palettes File Location, you would want that network folder read-only to most users, to avoid accidental revisions or deletions. (Unless your office is very small, all users are "power users" and you make provisions to back up the files, since even power users are not perfect.)