Open katelunceford opened 4 months ago
Q = Kate's questions A = Paige's answers
Q: How do y'all assign a seat/license to someone? A: I first purchased a set number of seats (they come in packs of 5). From there, we added the email addresses for our team members. One thing that's tricky is that if someone is added to a project, they are automatically assigned a seat. If you don't have enough seats, Asana will begin to charge you for it after a couple of weeks.
Q: Is there a particular workspace or environment (by team/function/etc.) that each seat is assigned? A: We have an OPM Team, which has members (who get seats). We can have separate portfolios under this team to group our projects.
Q: Do you know how you would reassign a seat to someone else? A: From the admin console, I can add and remove team members.
Shelby's questions for the demo (because she'll be OOO)
Asana demo by OPM #18991
Let's decide if TPW has a big enough need for Asana's enterprise offering, or if we should at least centralize current licenses. Two work groups in TPW have already paid for licenses (separately, on their own) to the Asana project management software. Another group is actively interested in it, and more groups may be, too.
If the same software is being paid for by multiple groups in TPW, it should be pooled into one budget item under DTS. Let's be holistic instead of 2 procard contracts. DTS isn't here to say yes or no, but we need to be aware of each group's needs.
Questions to answer
OPM - likes it, just implemented it
SMP - doesn't like it, bought it in April
SBO - wants to implement it
Notes & references