<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jaime J. on Medium]]></title>
        <description><![CDATA[Stories by Jaime J. on Medium]]></description>
        <link>https://medium.com/@jaimejhwacinski?source=rss-b02e912dc860------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DcwWP5MwBgrKn4HL.</url>
            <title>Stories by Jaime J. on Medium</title>
            <link>https://medium.com/@jaimejhwacinski?source=rss-b02e912dc860------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:06:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jaimejhwacinski/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building Coda’s single-sign-on]]></title>
            <link>https://medium.com/coda-project/building-codas-single-sign-on-2b8ed1bf955c?source=rss-b02e912dc860------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b8ed1bf955c</guid>
            <category><![CDATA[login]]></category>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Jaime J.]]></dc:creator>
            <pubDate>Wed, 11 Dec 2019 18:34:53 GMT</pubDate>
            <atom:updated>2019-12-11T18:34:53.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MAeoMKWDZC4JQXs0XFawOA.png" /></figure><p>Most blogs you read from Coda range from our 50,000ft view of the world to a single new feature that we are excited to share with you. This blog is about a somewhat dry, yet highly critical Enterprise feature, and how we made decisions during development.</p><p>Welcome to the world of authentication through single-sign-on (or lovingly known as SSO)!</p><h3>An abridged history of authentication.</h3><p>What does authentication actually mean? Authentication is rooted in how we trust one another. We need to be able to prove we are who we say we are.</p><p>The notion of authentication dates at least as far back as the Ancient Roman Empire, where soldiers would use watchwords to prove loyalty. Watchwords, passwords literally etched into a block of wood, were physically transported from place to place. Unfortunately for those soldiers, watchwords were slow, easy to steal, and scenario-specific.</p><p>Proving your identity became increasing more complicated as the digital age evolved and people all over the planet started connecting via the Internet. Without the physical manifestation of a password, how do you prove you are YOU? We rely on a short string of characters—a digital password.</p><p>Protecting and using that little password has evolved many times, from using a salted hash (no, it’s not a morning breakfast food) to captchas (those things you thought were mini-games for choosing the images with birds in them) to biometrics (which movies portray cooler than reality). The key is to remember that all authentication technology will evolve over time to ensure your identity is protected and to keep pace with fast changing technology in the era of SaaS.</p><p>At Coda, your company’s employees and content are serious business to us. We are thrilled to provide the ability to authenticate with Coda via SSO through the open standard Security Assertion Mark-up Language (SAML) 2.0 protocol.</p><h3>Building SSO behind the scenes.</h3><p>As Coda’s popularity in large organizations has grown, the requests to IT-manage Coda like other corporate software has also increased. Even though our Business Platform team just shipped our billing platform and the new Workspace/member model, we knew we needed to provide it fast.</p><p>As context, our current authentication method only supports customers signing up with their Google accounts. As a relatively new company, we leveraged a well known authentication and permission provider to get up and running fast. We started by leveraging Google Authentication, which also provided the ability to use a known file system solution for storing access permissions, providing full text search, etc. To provide a new authentication mechanism for Coda, we needed to re-examine our existing Google Drive integration, where we authoritatively store doc access control lists (ACLs) or who has what level of access to the doc, and how workspaces/domains are managed.</p><p>Every possible SSO choice was analyzed and discussed (in a Coda doc, of course). After we answered the higher-level questions, we drew out an end-to-end outline to map user experience. These scenarios included a set of UI mocks that helped us brainstorm ways to support both Google Drive ACLs and Coda ACLs.</p><p>Ultimately, from a prioritization perspective, SSO helped us accomplish a few things:</p><ol><li>Build some of the common components that we will leverage for enabling other login mechanisms in the future</li><li>Slipstream into existing best practices for companies that use a single-sign in solution</li><li>Facilitate login via Azure AD &amp; Okta for Coda’s Enterprise Customers</li></ol><h3>Storing ACLs.</h3><p>By introducing SSO, our users would not be signing in via Google, and we would not have a Google authentication token for them — meaning we could not store ACLs in Google Drive for these users. So, when creating a new doc or changing the sharing settings for a doc, we’d need to provide a way to ensure the user has permission to edit permissions on the doc.</p><p>We had a few models to consider, each with a list of effects and pros and cons. We took our investigation to a weekly meeting called the “Coda Catalyst” to pull feedback from other Codans through the <a href="https://coda.io/t/Question-Voting-and-Polling_tRlEOimN6EU">topic voting template</a> and the <a href="https://coda.io/t/Team-Pulse-Check-Tracker_tIQX_yM7MYa">sentiment template</a>. (Highly recommend using these templates for gathering quality feedback.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5LYAKO9el3CZd1yRPFMpRQ.png" /></figure><p>After incorporating the feedback we received, we landed on a model that looks at the user account and Organization settings to determine where to store the ACLs for the doc. This model left us with the most flexibility to extend the experience in future scenarios and also continues the current benefits of Google Drive integration for existing Google users.</p><p>So now a user may see docs in a workspace whose ACLs are stored in either Coda or Google (though, never both at the same time).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVqgRq1EdSoz_5PqRI1Zag.png" /></figure><h3>Sounds great. How do I setup SSO?</h3><p>Through our Enterprise plan, your company can now choose to manage Coda in your app portfolio with your favorite identity provider (e.g., Okta or Azure Active Directory).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cU2GXl7CZ_q5qil0tvbn2w.png" /></figure><p>We will walk your Organization admin through SSO setup and management. If your company chooses to use SSO, your document permissions will be stored in Coda instead of Google Drive. Find <a href="https://help.coda.io/en/articles/3520174-getting-started-with-sso">more information here</a>.</p><h3>What’s next?</h3><p>The Business Platform team is working on many great new features for Workspaces and Members. We are also working on simplifying the ability to add and remove members in Coda with the SCIM protocol … but that’s another story. Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b8ed1bf955c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coda-project/building-codas-single-sign-on-2b8ed1bf955c">Building Coda’s single-sign-on</a> was originally published in <a href="https://medium.com/coda-project">Coda Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New building block: Layouts]]></title>
            <link>https://medium.com/coda-project/new-building-block-layouts-6337b28a4ca7?source=rss-b02e912dc860------2</link>
            <guid isPermaLink="false">https://medium.com/p/6337b28a4ca7</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Jaime J.]]></dc:creator>
            <pubDate>Fri, 09 Nov 2018 20:07:03 GMT</pubDate>
            <atom:updated>2018-11-10T16:09:46.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ie0GzPM5-YHJPbDIYrPk0w.png" /></figure><p>One of our most important building blocks — Views — just got much more powerful. Now you can customize your data down to the very row, zooming in what’s important and hiding the rest.</p><p>Before now, Views could be visualized as cards, calendars, or Gantt charts. However it was displayed, though, you could never get the perfect View of a single row. Starting today, you can do just that. We call it Layouts.</p><blockquote>Want to play with Layouts? Check out our new <a href="https://coda.io/t/Boxs-Candidate-Coordination-Doc_tBgNyOvzJ8e?utm_campaign=layouts-20181109&amp;utm_medium=blog&amp;utm_source=coda">Candidate Scheduling</a>, <a href="https://coda.io/t/Sales-CRM_t5B049RYQVY?utm_campaign=layouts-20181109&amp;utm_medium=blog&amp;utm_source=coda">CRM</a>, <a href="https://coda.io/t/Flexible-Invoice-System_tk4xB4FCFaS">Invoice</a>, and <a href="https://coda.io/t/Charity-Auction-Book_tNzsGsyTP_g?utm_campaign=layouts-20181109&amp;utm_medium=blog&amp;utm_source=coda">Auction</a> templates in the Gallery!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pFM1-ya-TU3s7j7F" /></figure><p>This new Layout building block focuses on how to better visualize what’s inside of each row. To get started, open a row and click the new “edit” icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-4yUHLKnkZGuaKuZnmqvpA.gif" /></figure><p>When creating a new layout there are a few styles to choose from as a starting point. Once you select an option, drag and drop fields around until you’re happy with the design. You can even name and save it to re-purpose later.</p><p>We’re also introducing a new Detail view which puts your newly customized row front and center in your doc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*Om61Q-L-hdBRJ2eMFf6Ywg.gif" /></figure><h3>Building the building block.</h3><p>At Coda, we believe docs can be as powerful as apps. And often, there are three parts to apps: data, interaction and presentation. Today’s launch combines the last two: How do you enable makers to present and interact directly with their data in a functional and beautiful way? How can a table tell a story?</p><p>To answer these questions, our designers and engineers referenced countless websites, apps, and print media to survey how they tell stories with data. Eventually common patterns emerged. And we began to recite a mantra: Everything’s a table.</p><p>To show you what I mean, let’s take a familiar example. Yelp. Imagine Yelp as one giant table, where each restaurant makes up a row. And within that, you have attributes: the reviews, the location, the menu. Those are the columns. Looking at the Yelp page below, you can see that every part maps to a building block in Coda. The carousel of imagesーcards. Each individual reviewー a sub-table. The average score? A formula. Now I’m not saying you should build Yelp on Coda tomorrow — just want to drive home the idea that tables and rows are everywhere if you look closely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSIhgzAHshxgzXcUnYCGww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w29WMXGs-c6rXox63Phg3g.png" /></figure><p>You can have however as many components as you want, but if you want users, you need to tell a story with them. Each restaurant may be a row, but nobody wants to read through a long row with a vertical list of attributes to decide where to eat. You want a way to shine a light on a detail. You want a way to zoom in on what’s important and do what you need to do. Look at the pictures. Read the menu. Make a reservation. Done.</p><p>In that spirit, our team decided on three guiding principles to help us bring Layouts to life.</p><p><strong>Principle 1: Keep it row-level.</strong></p><p>The first principle was to focus on viewing and interacting at the row level. When we started to experiment with real makers’ scenarios, like building an invoice or a recruitment system, we stumbled across a big usability gap. Looking at a row, you lost track of all the lookups and references to the rest of the doc. Like when you want to see a set of sub-tasks for a big project, invoice items for a purchase order, or a set of references for a recruiting candidate. So we expanded those references in-place so the user could meaningfully interact with them from deep within a row. If one of your columns is looking up information from another table, you’ll be able to expand those references to see and edit them just like you would in their original location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HQrOUwEfpNhPBbc-2ClAPw.gif" /></figure><p><strong>Principle 2: Give makers something to start with.</strong></p><p>The second was giving people inspiration to get started. This led us to providing a bunch of layouts to choose from in order to get started, called quick styles. We’ll be adding lots more over time. This first set optimizes for common shapes of data. For example, visually heavy vs text heavy vs calculation heavy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pfoeg1uENznFaq2D58GC8w.png" /></figure><p><strong>Principle 3: Put details center stage.</strong></p><p>The third guiding principle was to bring the freshly customized row to the center stage of the doc where it made sense. This effectively led us to our new Detail view where you could take today’s pop-out of a row and anchor it to the body of your doc. This is great when working with scenarios that have a more singular focus on each item in a table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMM3FGEqHOrsQjExANi7Ww.png" /></figure><p><em>I think this new building block will really change the face of your docs. We can’t wait to see how you Coda with Layouts.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6337b28a4ca7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coda-project/new-building-block-layouts-6337b28a4ca7">New building block: Layouts</a> was originally published in <a href="https://medium.com/coda-project">Coda Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>