How does everyone document their Workfront setup? | Community
Skip to main content
S
Stacey_Robertson
Level 5
January 17, 2024
Solved

How does everyone document their Workfront setup?

  • January 17, 2024
  • 3 replies
  • 1188 views

I am working on an inherited instance and we are getting another new system admin soon.  During the Admin 101 call it was mentioned that you could use a project to document tips, links, etc.  For anyone doing that, can you share how you have it set up?  Do you use a custom form to gather information, post updates or attach documents?  Just looking for ideas on best practice and what works for you.  If you have fusion documented, we'd also be interested in what processes you use for that.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by VicSellers

Hi @stacey_robertson - We do this! We use a project and utilize requests in the project (one request/issue per topic). I prefer requests for this instead of tasks because you can also setup a queue in the project and then have the custom form attached already to fill out when you create a new request (pretty much a private request queue setup). Then, there is a report within a dashboard that has all of the requests with relevant information (Topic/Topic Description/Additional Tips as columns or links to documentation).

3 replies

VicSellers
Community Advisor
VicSellersCommunity AdvisorAccepted solution
Community Advisor
January 17, 2024

Hi @stacey_robertson - We do this! We use a project and utilize requests in the project (one request/issue per topic). I prefer requests for this instead of tasks because you can also setup a queue in the project and then have the custom form attached already to fill out when you create a new request (pretty much a private request queue setup). Then, there is a report within a dashboard that has all of the requests with relevant information (Topic/Topic Description/Additional Tips as columns or links to documentation).

    S
    Sujatha_TS
    Level 4
    January 17, 2024

    Hi Stacey, 

    here are few things we have followed: 

    1. Yes, we do have a project to onboard users and admins. with step by step instructions/ Admin 101 -- week 1 - understand team hierarchy - portfolio, program and project, job roles, resourcing, and how projects are set up; week 2 - taking lead on licensing and some admin drill (we can use WF admin audit blueprint here) week 3 - conduct office hours week 4 - start regular governance meetings 

    2. Making sure to house all QRGs, training materials and recordings for users to complete in process and training project.

    3. Admin to create "Workfront FAQ report" - this is really helpful.

     

    hope this helps. 

    KellieGardner
    Community Advisor
    KellieGardnerCommunity Advisor
    Community Advisor
    January 17, 2024

    I personally don't use Workfront to document our setup. I have a entire PDF document that has all the ins and outs of how the system is setup. It basically mimics the backend hierarchy of the setup options. My document is comprehensive documentation that also outlines company policies and procedures that align to the setup and any reasoning behind it. 

     

     

     

     I do use Workfront to track changes to setup, quick help links for my end users, and onboarding end users.

      C
      cverges
      Level 5
      January 17, 2024

      This is how we do it, too, though via Google Sheets (sorry, Adobe).  We also use LucidChart or other Visio-like tools for flow diagrams, UML sequence diagrams, etc.  These are especially helpful for the Fusion scenarios.

        Terms & ConditionsAccessibility statement

        Loading footer...