UpStream stores tasks, bugs, milestones, and files as serialized arrays inside the project's postmeta. SleekView unpacks those arrays at read time and treats each entry as a row, with the parent project post joined for context. The unpacking happens in PHP so it respects whatever structure UpStream actually wrote, including custom-field add-ons that nest extra keys inside each entry.

Yes. SleekView writes back through the same serialized structure UpStream expects, so the client-facing frontend and the admin UI both see consistent data. The agent UI validates the array shape before writing so a malformed edit can't corrupt the meta payload, which is a real risk with naive serialized writes.

Yes. That's the headline reason teams add SleekView to UpStream — the default UI is project-scoped. SleekView gives you cross-project task and bug lists in one view, with project and client visible as joined columns so you can scope by client tag without losing the cross-project breadth.

Yes. Each item type lives under a different meta key (_upstream_project_tasks, _upstream_project_bugs, _upstream_project_milestones, _upstream_project_files). SleekView builds a separate view per type, or combined views with a type column. Bugs and milestones especially benefit from cross-project queues since severity and due-date scans don't fit a project-by-project flow.

Yes. UpStream's Custom Fields add-on stores extra fields inside the serialized arrays. SleekView surfaces those fields as columns once you point it at them. The agent UI helps you pick which keys to expose, so a custom field like billing_phase becomes a sortable column without any custom code.

SleekView views are admin-side. Frontend client visibility is unchanged: UpStream's frontend continues to render as configured. Use SleekView for internal team views — agency staff, PMs, QA — while clients keep using the frontend templates the plugin already serves to them. The two layers don't overlap and don't conflict.

Yes when done correctly. Each write reads the existing serialized array, modifies the targeted entry, and writes the whole array back atomically. SleekView locks per-row at write time and validates the resulting structure against UpStream's expected shape before the update_post_meta call. Concurrent edits to different entries in the same project's tasks queue safely; concurrent edits to the same entry are serialized.

Yes. Frontend Edit writes back through the same serialized arrays SleekView reads and writes. Edits made via Frontend Edit show up in SleekView on the next read; edits made via SleekView show up in the frontend on the next render. The two coexist as alternative write paths into the same data, useful when different team roles prefer different surfaces.